I think the XML documents are just going to have to not lie.
It's an administrative hassle, but it seems that their statements are going to have to be updated when they are saved in a different code page.
Maybe I lack imagination ...
John Goodyear
ATS Benchmarking Team
Gaithersburg, MD.
| [EMAIL PROTECTED]
12/12/2003 10:49 AM
|
To: John Goodyear/Gaithersburg/[EMAIL PROTECTED] cc: ANDREW BOYNE <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: Re: XML::SAX, XML::SIMPLE on os390(Z/OS) |
John Goodyear <[EMAIL PROTECTED]> wrote on 12/12/2003 10:19:36 AM:
> Does the XML document define what code page it's in?
>
>
> John Goodyear
> ATS Benchmarking Team
> Gaithersburg, MD.
That is an excellent question, but unfortunately even with an
answer like "UTF-8" it may be meaningless on a z/OS platform
where the document in question was introduced as text that
was translated to CP 1047. In other words an XML header such
as:
<xml version="1.0" encoding="UTF-8">
is lying to you if you ftped that document to z/OS with XLAT
on, or if it was generated from a perl statement such as:
print XMLFILEHANDLE "<xml version\"1.0\" encoding=\"UTF-8\">\n";
That was run by the perl interpreter on z/OS.
The test documents that the XML::SAX perl extension
tests write out would face a similar encoding ambiguity
problem.
Peter Prymmer
