On 16 Jun 2009, at 22:15, Sam Fuqua wrote:
Hi Sam
> Unfortunately, my problem still seems to be the same. The console
> always logs that Arial cound not be found, so it is defaulting to
> "any", which I believe is mapped internally to 'Times'. I'm using
> Linux, so instead of Times New Roman, it's the Nimbus counterpart.
> When the pdf comes up, the Latin text displays as expected, though
> the Japanese text displays as '###', which would indicate a missing
> glyph. However, the character renders properly everywhere else on
> my system. I believe that the font has the glyph, but that FOP is
> having trouble finding it.
No, it means that FOP is trying to use the Base14 Times font, which
definitely does not contain any glyphs for non-western characters. The
fact that the characters render properly in a web-browser or word-
processor on your system means that those applications actually
perform font-selection behind the scenes (based on the availability of
glyphs for a specific Unicode codepoint)
With FOP 0.95 or earlier, the user has to make sure the text-blocks in
question have the correct font-family, in order to guarantee that they
are rendered correctly. As suggested earlier, this can be achieved by
wrapping Japanese words in a fo:wrapper with the right font-family.
For FOP Trunk, you can specify a list of font-families to try on the
fo:root or fo:page-sequence. FOP 0.95 is not yet as clever, and will
always only try the first family specified in the list in that case,
but Trunk will perform basic, per-word font-selection. Per-character
font-selection has not yet been implemented, but can be emulated by
inserting zero-width spaces as boundaries.
Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail:
fop-users-unsubscribe@...
For additional commands, e-mail:
fop-users-help@...