<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body style="">
<div>
<br/>Andrew Brunner <atbrunner@aurawin.com> hat am 26. September 2012 um 21:21 geschrieben:
<br/>>[...]
<br/>> If c-data contains any character whose ordinal value is greater than 127
<br/>> the XML parser raises an exception.
</div>
<div>
</div>
<div>
Have you tried setting the right encoding in the xml?
</div>
<div>
</div>
<div>
<br/>>[...]
<br/>> Is there a ANY case where dropping c-data is OK just because a user
<br/>> hasn't entered it? I'm just curious... I can't seem to find any good
<br/>> reason as to why this happened other than to force UTF or some other
<br/>> encoding on everyone.
<br/>>
<br/>> The XML parser already has options for Validation. I'm hoping to get
<br/>> someone on the team to add a one line if Validation=true then check the
<br/>> values else just parse it already.
<br/>>
<br/>> http://mantis.freepascal.org/view.php?id=22990
</div>
<div>
</div>
<div>
Sergei's note is correct:
</div>
<div>
</div>
<div>
---snip---
</div>
<div>
This is unrelated to validation. XML parser always checks that its input data conforms to the specified encoding.
<br/> The XML data should either be in utf8 encoding, or in utf16 with a BOM character at the beginning, or it should be labeled with 'encoding' attribute (additionally xmliconv unit must be added to uses clause if encoding is different from iso8859-1).
</div>
<div>
---snap---
</div>
<div>
<br/>
<br/>> Another thing would be to have an exception level event. There is an
<br/>> event there, but still the exception is raised the event is called -
<br/>> stopping the parsing and throwing a wrench in my streaming application
<br/>> logic.
</div>
<div>
</div>
<div>
Maybe you can explain what you are trying to do?
</div>
<div>
</div>
<div>
<br/>> In a world where XML is just about the primary choice for data
<br/>> transmission - I think we take speed as the ut-most priority and don't
<br/>> use such a pivotal technology as a tool to get what someone else wants.
</div>
<div>
</div>
<div>
AFAIK such statements have seldom a positive effect on volunteer projects.
</div>
<div>
<br/>
<br/>> The bottom-line inference here is that WE ALL must encode ALL DATA
<br/>> before it can be streamed / parsed. That's bad news and EXPENSIVE.
</div>
<div>
</div>
<div>
Well, whatever you try, you must at least encode all < > and & characters.
</div>
<div>
</div>
<div>
Mattias
</div>
<div>
</div>
</body></html>