Re: Problem with "oe" ligature

Le vendredi 03 d=E9cembre 2004 =E0 09:21 +0100, Melanie R=F6sch a =E9crit=
 :
> Hallo Julian,
>=20
> it seems that db2latex only provide characters in the Latin 1 range=20
> correctly.
> I found a solution to provide special characters and posted it on=20
> 11/18/04 at this
> newsgroup. It is not very nice but it works.

Strange, I didn't find that post in the archives of the mailing list.
However, I did find a solution that does not seem too ugly. If I
understand correctly, the situation is as follow :
1. From the XML document, db2latex generates a Latin1-encoded document
(the xsl:output encoding type is set to ISO-8859-1, cf. docbook.xsl)
2. As the oe ligature is not in that charset, the œ stays
untranslated in the LaTeX file.

This problem can be solved by having the output encoded in UTF-8, and by
having the Unicode packages included in the LaTeX preamble : put the
following in your custom stylesheet :
<xsl:output method=3D"text" encoding=3D"UTF-8" indent=3D"yes"/>
<xsl:param name=3D"latex.use.ucs">1</xsl:param>
<xsl:param name=3D"latex.inputenc">utf8</xsl:param>

Now, a question for the makers/gurus of db2latex : why choose an
ISO-8859-1 encoding by default, as the UTF-8 seems to be perfectly
fine ? Does the encoding change break something ?

--=20
Julien



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/