Re: DOCBOOK-APPS: Choosing a characterset for DocBook

["Christopher R. Maden" <crism at maden dot org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At 01:52 AM 3/15/02, Jens Stavnstrup wrote:
>The editing have been done on a Unix platform with Emacs. Occasionally,
>when copying text from a word document,  Saxon protests (actually
>Aelfred protests), complaining over "bad continuation of multi-byte UTF-8
>sequence", which have been a problem, since I have chosen the ISO-8859-1
>encoding (don't remember why).

The parser obviously is not aware that you have chosen ISO 8859-1.  That is 
the expected error message if an 8859-1 document contains any high bytes 
(128+) and the parser is trying to parse it as UTF-8.

1) Do all of your entities (i.e., files) have encoding declarations?  What 
are they?  Remember that UTF-8 is the default unless you explicitly specify 
a different encoding (or use a byte-order mark, in which case UTF-16 is the 
default).

2) How are you invoking the parser?  From within SAXON, obviously - is 
SAXON being called from the command line, or within another program?  What 
exactly are the parameters it's being passed?

~Chris
- -- 
Christopher R. Maden, Principal Consultant, crism consulting
DTDs/schemas - conversion - ebooks - publishing - Web - B2B - training
<URL: http://crism.maden.org/consulting/ >
PGP Fingerprint: BBA6 4085 DED0 E176 D6D4  5DFC AC52 F825 AFEC 58DA
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8

iQA/AwUBPJHHt6xS+CWv7FjaEQLVtACeK8vhtpW0lR1Lglhu7WVezv7JmC4AoLa9
W3ZjhuuDFZojp05ANUG/pp56
=GoOY
-----END PGP SIGNATURE-----