>> I've tried to create entities in the DTD like: <!ENTITY aring "å">
and
>> then it works better - getNodeValue on "å" then gets me the right
>> character.. But using the DOMPrint code on a document as that gives me
>> "&ring;"...
>
>It's kind of irritating to have to do that, given that 8859-1 is a
>standard encoding, the parsers should recognize å if your're
>encoding is set properly. I had a lot of trouble with 'è',
>'é', etc. when converting Roget's thesaurus to XML. I finally
>had to declare them in the DTD as you had to.
Lots of encodings are standard encodings. If we had to hard code every one
of the possible named character refs into the parser, it would be too much
of a burden. It makes a lot more sense to have standard DTD fragments out
there that define sets of them, and you just get them and include them into
your DTD as required.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]