I don't have a big opinion, but clearly this is a much bigger issue than
Xerces and would apply equally to all other parsers I would guess. There are
a lot of different deployment scenarios to consider.
--------------------------
Dean Roddey
The CIDLib C++ Frameworks
Charmed Quark Software
[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
Subject: Re: Special character coding
> "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 have to be parsed in
> > from user's DTDs, when they want it to happen, otherwise, the parser
> > would have thousands of predefined entities. How those external DTDs
> > get defined and passed around is another issue altogether.
>
> 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.
>
> jas.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
