From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Strange that DOMPrint screws it up. I tested a small piece of my
> roget.xml against SAXPrint, SAX2Print, and DOMPrint. DOMPrint got it
> wrong, the other two got it correct.
>
> $ DOMPrint -v=auto /tmp/tst.xml
>
> ...
>
>
> L
On 30 May 2001 20:30:24 -0600, Jason E. Stewart wrote:
>Would it be useful to distribute the DTD's with Xerces? Or does it
>make more sense to have them available as external documents. We could
>make them available off the WWW site.
Or people could just download
http://www.w3.org/TR/xh
tware
[EMAIL PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
- Original Message -
From: "Jason E. Stewart" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 7:30 PM
"Dean Roddey" <[EMAIL PROTECTED]> writes:
> I don't have a problem if people want to contribute DTD fragments
> that cover particular encodings, and if those get distributed with
> the parser. I was just saying that they couldn't be prebuilt into
> the parser itself as predefined entities. They h
PROTECTED]
http://www.charmedquark.com
"Why put off until tomorrow what you can
put off until the day after tomorrow?"
- Original Message -
From: "Jason E. Stewart" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 7:06 PM
Subject: Re: Special chara
"Dean Roddey" <[EMAIL PROTECTED]> writes:
> 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
>> I've tried to create entities in the DTD like:
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
>> "˚"...
>
>It's kind of irritating to have to do that, given that 8859-1 is a
>standard encod
"Stefan Berglund" <[EMAIL PROTECTED]> writes:
> I've tried to create entities in the DTD like: 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
> "˚"...
It's kind of irritating to have to do tha
"But using the DOMPrint code on a document as that gives me "˚"..."
Its escaping the & sign. In some cases that might be what you want, if you
want to keep the character in the å form after you parse the resulting
XML. If you want the å to be parsed to the actual code point, then it
shouldn'
