|
From: Eric B. <e.b...@no...> - 2001-05-21 15:41:00
|
Le Saturday 19 May 2001 08:57, Daniel Veillard a =E9crit : > 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. I know probably as much, or less, as Norm. Here is what I know SP (jade, SX, etc) has defined rules about the encoding to use. These rul= es=20 are based on the document's contents as well as the system's default=20 character set and environment variables. The detailed rules are on: http://www.jclark.com/sp/charset.htm > BTW, if automatic encoding detection is not possible, is there a way in > DocBook to indicate the encoding if known (for example on the root elem= ent) > ? If this detection/advertizing requires human input, it would be great= to > have to deal with it only once. --=20 +----------------------------------------------------------------------+ | =C9ric Bischoff mailto:e.b...@no... = | +----------------------------------------------------------------------+ |