Blame docs/locale.xml

Packit 0f19cf
Packit 0f19cf
Packit 0f19cf
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd">
Packit 0f19cf
<section xmlns:xi="http://www.w3.org/2001/XInclude">
Packit 0f19cf
<title>Locale Support</title>
Packit 0f19cf
Packit 0f19cf
<section id="sec-doc-encode">
Packit 0f19cf
<title>Document Encoding</title>
Packit 0f19cf
Packit 0f19cf
<para>By default the latex document produced by <command>dblatex</command> is
Packit 0f19cf
encoded in latin1, that fits well for roman-characters. This said,
Packit 0f19cf
a real international support involves some kind of Unicode (UTF8)
Packit 0f19cf
support.</para>
Packit 0f19cf
Packit 0f19cf
<para>In dblatex, the Unicode support is done by two methods that can be selected
Packit 0f19cf
by some parameters:
Packit 0f19cf
Packit 0f19cf
<itemizedlist>
Packit 0f19cf
<listitem><para><parameter>latex.unicode.use</parameter>=1 asks for including the
Packit 0f19cf
unicode package (initially provided by Passivetex) in order to
Packit 0f19cf
handle many of the unicode characters in a latin1 encoded document.</para>
Packit 0f19cf
</listitem>
Packit 0f19cf
<listitem><para><parameter>latex.encoding</parameter>=utf8 produces a document
Packit 0f19cf
encoded in UTF8, that is compiled in UTF8. It requires to have the
Packit 0f19cf
<literal>ucs</literal> package installed.</para>
Packit 0f19cf
</listitem>
Packit 0f19cf
</itemizedlist>
Packit 0f19cf
</para>
Packit 0f19cf
Packit 0f19cf
<para>In some languages like Chinese, Japanese or Korean, the latex document
Packit 0f19cf
must be in UTF8. Therefore, the UTF8 encoding is forced for these languages
Packit 0f19cf
whatever the parameter values are.</para>
Packit 0f19cf
Packit 0f19cf
</section>
Packit 0f19cf
<section><title>Babel Languages</title>
Packit 0f19cf
Packit 0f19cf
<para>Dblatex should be able to handle most of the languages supported by the
Packit 0f19cf
babel package. Just set the
Packit 0f19cf
<literal>lang=<replaceable>lang</replaceable></literal> attribute in the root
Packit 0f19cf
document element and dblatex will load
Packit 0f19cf
the appropriate babel language.</para>
Packit 0f19cf
Packit 0f19cf
</section>
Packit 0f19cf
<section><title>CJK Languages</title>
Packit 0f19cf
Packit 0f19cf
<para>Dblatex can handle the CJK languages thanks to the CJK package. The CJK
Packit 0f19cf
package must be installed to have this support available.</para>
Packit 0f19cf
Packit 0f19cf
<para>As said in <xref linkend="sec-doc-encode"/> the latex file is encoded
Packit 0f19cf
in UTF8. Moreover, the Cyberbit fonts are then used.</para>
Packit 0f19cf
Packit 0f19cf
<para>The install of the CJK package and Cyberbit fonts are well described at:
Packit 0f19cf
<ulink url="http://kile.sourceforge.net/Documentation/html/cjk.html"/>.
Packit 0f19cf
</para>
Packit 0f19cf
Packit 0f19cf
<section><title>Korean Support</title>
Packit 0f19cf
Packit 0f19cf
<para>Dblatex does not use the HLatex package to drive Korean documents. It does
Packit 0f19cf
not use the <command>hmakeindex</command> nor the <command>hbibtex</command> tool.
Packit 0f19cf
Currently, Korean is handled like Chinese and Japanese with the CJK package.</para>
Packit 0f19cf
Packit 0f19cf
</section>
Packit 0f19cf
</section>
Packit 0f19cf
Packit 0f19cf
<section><title>Mixing the languages</title>
Packit 0f19cf
Packit 0f19cf
<para>Dblatex cannot handle correctly a document containing several elements
Packit 0f19cf
with different <sgmltag>lang</sgmltag> values. In particular, if the main
Packit 0f19cf
document lang is not one of the CJK language, a portion of text written in CJK
Packit 0f19cf
will not be handled correctly and it can result in a compilation crash.</para>
Packit 0f19cf
<para>Even if the langs mixed do not end to a compilation failure, only the
Packit 0f19cf
main document lang will be taken into account.</para>
Packit 0f19cf
</section>
Packit 0f19cf
</section>