Ah gotcha.

We need an encoding property on Document that we can set when parsing; then this can be defaulted into the XMLWriter by default. Shouldn't be too hard to do; any volunteers? :)


On 24 Nov 2003, at 14:57, Klaus Engelhardt wrote:


Dear James Strachan,

Thanks, but that's not what I needed. I knew that already, it's very
nicely described in the Dom4J cookbook. Of course I can output a
document in any encoding I choose. But I don't know which encoding
to set because I don't know the original encoding!

What I need is to find out the encoding of an existing document,
so can I modify the document, and then output a new version in the
original encoding. If I just use the default, Dom4J makes everything to
UTF-8; if I explicitly set one I might choose the wrong encoding.

Thanks for the quick response, and hopefully, for your answer to my
real question.

Best regards,
Klaus Engelhardt

Klaus Engelhardt
Metzstr. 8
81667 München
Tel. 0049/89/483491 (home)
Tel. 0049/89/3299-1409 (work)



James ------- http://radio.weblogs.com/0112098/



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user

Reply via email to