On 29 Jan 2009, at 18:46, mpanhuijsen wrote:
Hi Mathijs
I tried the following:
-Change every reference to my default font from Verdana into
ARIALUNI (the
name of the .ttf file).
-Create a dir c:\myfonts\ and copy ARIALUNI.ttf and ARIALUNI.xml
(generated
metric font file) into it
-Remove autodetect from my fop config file.
-Added the following fragment:
Can you try again with FOP 0.95 (using the setup as mentioned in your
initial post), and see if the issue persists?
Looking at your FO file, the correct characters/codepoints are used
there, so that cannot be the problem.
<font-triplet name="ARIALUNI" style="normal"
weight="normal"/>
And still I'm seeing the Serif font and no Japanese characters.
Yes, now you get the # character again, which means FOP cannot find
the glyphs for the characters in the used font. This means that
ARIALUNI.ttf is not properly registered. You should at least see a
warning about FOP falling back to Serif during processing.
The reason could be that <font-triplet /> alone is not enough. Did you
forget to paste a piece of the config-file? (the surrounding <font />
element?)
Another thing to look out for (if you have used FOP 0.20.5 in the
past) is that font-configuration should be specified in the config-
file for each renderer separately. See the example fop.xconf in the
distribution.
Try running FOP with debug output enabled (-d). This should tell you
more about the font-files that are parsed.
Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
