blocks|key|1939149|text|为什么第三方不能可靠地解决这个问题？如果他们的XML中包含非法字符，我敢打赌这是一个合法的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1939150|话虽如此，为什么不在使用str_replace解析字符之前将其删除呢|offset|length|1939151|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/function.str-replace.php^0|0|C|B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Why can't the 3rd party reliably fix this issue? If they have illegal characters in their XML, I would wager that it's a valid issue.

Having said that, why not just remove the character before you parse it using <a href="http://php.net/manual/en/function.str-replace.php" rel="nofollow">str_replace</a>?

blocks|key|1883083|text|只要字符串是有效的UTF-8，就可以使用str_replace()。请注意，str_replace()将处理字节偏移量，因此您将不再处理PHP字符串，而是处理字节字符串。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1883084|这就是问题所在:如果您的第三方包含随机的空格和控制字符，而这些字符在XML中没有任何用处，那么您不妨假定它们最终会破坏UTF-8。因此，您不能自信地使用str_replace()+(只有在善意的情况下)，直到您确定它们当前的转储并非完全无用。|1883085|也许您可以选择一条捷径，将其填充到libxml+DOMDocument对象中，并使用@抑制错误，让libxml库来处理错误。类似于：|1883086|$doc+=+new+DOMDocument();
if(@$doc->loadXML($raw_string))+{
++//+document+is+loaded.+time+to+normalize()+it.
}
else+{
++throw+new+Exception("This+data+is+junk");
}|code-block|syntax|javascript|1883087|entityMap^0|K|D|12|D|0|24|D|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|Z|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

You can use <code>str_replace()</code> provided that the string is valid UTF-8. Note that <code>str_replace()</code> will then work with byte offsets, so you are no longer dealing with PHP strings but with byte strings.

And there is the rub: if your 3rd party includes random whitespace and control characters that serve no purpose in XML, you might as well assume they eventually break UTF-8. So you can't use <code>str_replace()</code> with confidence (only in good faith) until you have ascertained that their current dump of the day is not entirely useless.

Maybe you could take a shortcut and stuff it in a libxml DOMDocument object and suppress errors with @, leaving the libxml library to deal with errors. Something like:

<pre><code>$doc = new DOMDocument();
if(@$doc-&gt;loadXML($raw_string)) {
 // document is loaded. time to normalize() it.
}
else {
 throw new Exception("This data is junk");
}
</code></pre>

blocks|key|2707530|text|为什么你和第三方要用XML交换数据？想必双方都希望通过使用XML而不是某种随机的专有格式来获得一些好处。如果允许他们生成糟糕的XML+(我更喜欢称之为非XML)，那么任何一方都得不到这些好处。改正他们的生活方式符合他们的利益。试着说服他们这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2707531|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Why are you and the third party exchanging data in XML? Presumably both parties expect to get some benefits by using XML rather than some random proprietary format. If you allow them to get away with generating bad XML (I prefer to call it non-XML), then neither party is getting these benefits. It's in their interests to mend their ways. Try to convince them of this.

I'm using XMLReader to parse XML from a 3rd party. The files are supposed to be UTF-8, but I'm getting this error:

<code>parser error : Input is not proper UTF-8, indicate encoding !</code>

<code>Bytes: 0x11 0x72 0x20 0x41 in C:\file.php on line 166</code>

Looking at the XML file in notepad++ it's clear what's causing this: there is a control character <a href="http://en.wikipedia.org/wiki/Device_Control_1#Device_Control" rel="nofollow">DC1</a> contained in the problematic line. 

The XML file is provided by a 3rd party who I cannot reliably get to fix this/ensure it doesn't happen in the future. Could someone recommend a good way of dealing with this? I'd like to just do away with the control character -- in this particular case just deleting it from the XML file is fine -- but am concerned that always doing this could lead to unforeseen problems down the road. Thanks.

Handling Encoding Errors While Reading XML With PHP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在使用XMLReader解析来自第三方的XML。这些文件应该是UTF-8格式的，但我得到了这个错误：parser error : Input is not proper UTF-8, indicate encoding !Bytes: 0x11 0x72 0x20 0x41 in C:\file.php on li...

问在使用PHP读取XML时处理编码错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在使用PHP读取XML时处理编码错误EN