blob: c5b896f51f5e84241ea262763ad0ac4d086e7e9e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
<?xml version="1.0" standalone="no"?>
<s1 title="Configuration">
<s2 title="How to configure Fop">
</s2>
<s2 title="setting up hyphenation">
<p>Fop comes already with some hyphenation pattern. If you need a hyphenation pattern
which isn't included in the distribution, do the following:
</p>
<p>1. get the TeX hyphenation pattern file and turn it into an xml file which conforms
to the hyphenation.dtd in the sub directory /hyph
</p>
<p>2. name this new file following this schema: languageCode_countryCode.xml. If you don't need
a country code, leave it away, p.e. the file name for an American english hyphenation pattern
would look like this: en_US.xml. For an Italian file: it.xml. Language and country codes must be
the same as in xsl:fo, that is follow
<jump href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO 639</jump>
and <jump href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO 3166</jump>
respectively. NOTE: The ISO 639/ISO 3166 convention is that language names are
written in lower case, while country codes are written in upper case.
</p>
<p>3. If you have build your new hyphenation pattern file successfully there are
two ways to make it accessible to Fop.
</p>
<p> a) Put this new file into the directory /hyph and rebuild Fop. The file will
be picked up and added to the fop.jar.
</p>
<p> b) Put the file into a directory of your choice and specify this directory
in the userconfig.xml in the entry <hyphenation-dir>.
</p>
</s2>
</s1>
|
