|
From: Norman W. <Nor...@ea...> - 2001-05-19 16:47:58
|
/ Daniel Veillard <vei...@re...> was heard to say:
| On Fri, May 18, 2001 at 03:48:05PM -0400, Norman Walsh wrote:
| > / Dan Mueth <d-...@uc...> was heard to say:
| > | How do these deal with the lack of encoding specification for DocBook/SGML
| > | docs? It isn't obvious to me why it is a problem for XML docs and libxml2
| > | but not for SGML docs with jade/SP.
| >
| > I'm not sure.
|
| Argh, if you don't know, who will ... Maybe we will have to ask James.
The answer occurred to me while I was working in the garden this
morning. While XML has a fixed SGML Declaration, SGML does not. So if
you want to use some character encoding other than the one described
by the reference concrete syntax, you have to provide the SGML
Declaration that indicates what characters are used (and what they
mean).
Although now that I write this, I'm not sure if that's the whole answer.
Just because I say that code point 0xED is a name character that doesn't
tell the processor what glyph to use. Hmm...
Be seeing you,
norm
--
Nor...@Su... | Resist the urge to hurry; it will only slow
XML Standards Engineer | you down--Bruce Eckel
Technology Dev. Group |
Sun Microsystems, Inc. |
|