You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Neil Graham <ne...@ca.ibm.com> on 2003/08/28 21:02:08 UTC
Re: 12436 - UTF-8 transcoder is not strict (and therefore not secure) .
Hi David,
Section 4.3.3 of the XML 1.0 spec, 2nd Edition [*], states
[[
It is a fatal error if an XML entity is determined (via default,
encoding declaration, or higher-level protocol) to be in a certain encoding
but contains octet sequences that are not legal in that encoding.
]]
So an option like this would run directly counter to the spec. And would
promote non-interoperability with other XML processors, which can be
expected to reject such documents.
It's just too bad that Xerces-C was non-conformant in this respect for so
long. It's to be regretted that this will cause some folks some pain. But
it's pain that would be felt when the documents have to be fed to some
other processor anyway, so I guess it's just a matter of now or later...
Cheers,
Neil
[*]: http://www.w3.org/TR/REC-xml#charencoding
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@ca.ibm.com
|---------+---------------------------->
| | David Schulze |
| | <davids@delorme.c|
| | om> |
| | |
| | 08/28/2003 02:30 |
| | PM |
| | Please respond to|
| | xerces-c-dev |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: "'xerces-c-dev@xml.apache.org'" <xe...@xml.apache.org> |
| cc: |
| Subject: 12436 - UTF-8 transcoder is not strict (and therefore not secure) . |
| |
| |
>---------------------------------------------------------------------------------------------------------------------------------------------|
12436 - UTF-8 transcoder is not strict (and therefore not secure).
Xerces 2.3.0 fixed bug #12436, unfortunately my company has shipped some
XML
files that do not conform to this. (The trade-mark symbol) So newer code
that uses version 2.3.0 cannot parse these older files. Is there a way for
me to turn off the validity checking of multi-byte sequences when using
UTF-8 that does not require modification to the XML file itself? Perhaps
some switch I can set before beginning a parse?
Thanks for any help.
David Schulze
DeLorme Mapping
Yarmouth, Maine, USA
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
mess with
Posted by Sébastien Demers <sd...@popupsolutions.com>.
In several files iostream.h, is still used in favor of iostream
Since the file iostream.h is obsolate. Why new revisions still using this
file instead of using iostream with a small using std::cout; ????
Please have a look in the file
xerces/c/src/xercesc/framework/StdOutFormatTarget.cpp for a party of mess.
- Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org