Re: [docbook] invalid characters for ISO-8859-1 response

["Anthony Ettinger" <anthony@chovy.com>]

On 10/31/07, Bob Stayton <bobs@sagehill.net> wrote:
> ----- Original Message -----
> From: "Anthony Ettinger" <anthony@chovy.com>
> To: "Dave Pawson" <davep@dpawson.co.uk>
> Cc: <docbook@lists.oasis-open.org>
> Sent: Wednesday, October 31, 2007 11:20 AM
> Subject: Re: [docbook] invalid characters for ISO-8859-1 response
>
> >
> > I'm still confused though...why make a doc require UTF-8, when if I
> > just typed it out there would be no dependency.
>
> UTF-8 output is not required, as the customization examples demonstrated.
> You can additionally customize the gentext strings to replace the
> non-breaking spaces.
>
> If you are wondering why UTF-8 is the default output encoding, that's
> because the DocBook XSL stylesheets support 59 languages, and the easiest
> way to do that is using Unicode, for which UTF-8 is the most commonly
> supported encoding.  Does that help?
>


Sure, unicode makes sense...I could be missing something but I
would've left entity references alone...I still don't see what is
gained by converting &#140; vs. just leaving it as &#140; in the
output...or simply leaving it as a space.




-- 
Anthony Ettinger
Ph: 408-656-2473
var (bonita, farley) = new Dog;
farley.barks("very loud");
bonita.barks("at strangers");

http://chovy.dyndns.org/resume/
http://utuxia.com/consulting