From: Michael B. <mbn...@mb...> - 2003-02-14 22:09:10
|
Wolfgang, > That's true. I just had a look at the problem and found that > I still have to fix the xpath parser code to include the full > range of valid characters into element names. I simply forgot > about that, so thanks for reminding me. I will > post a bug-fix once I got it working. Thanks for looking into this. I think the problem does indeed need fixing, because there will always be determined 8859-N people wanting to use eXist without transcoding. > The same applies to document display: When printing to stdout, Java > always converts the character encoding to its default, regardless of the > character encoding you specified for the document. If you use eXist to > store the content to a file, the character encoding should be ok. I'm not sure I understand this particular aspect. My final point about the sample I posted was that the file retrieved by the get document command had the correct encoding (ISO-8859-1 as stored) but a wrong encoding declaration in the XML header (utf-8). As far as I can see, this also happens when storing to a file. If I'm right about that the output file wouldn't (shouldn't) parse correctly. Michael Beddow |