Hi Andreas, 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.
I really hate asking such an open-ended, vague question, but do you have any ideas why it would not be finding that glyph? Sam On Tue, Jun 16, 2009 at 1:03 PM, Andreas Delmelle < [email protected]> wrote: > On 16 Jun 2009, at 17:09, Sam Fuqua wrote: > > Hi Sam > > Just to make sure that I'm understanding what you you're saying: >> * the <auto-detect> tag will cause FOP to detect my fonts >> * in order to print non-Latin text in non-Latin fonts, I need to >> specify which font family to use >> What is the purpose of the font-selection-strategy property? If I don't >> need character by character font specification, is this a way to >> automatically have non-Latin text rendered using a non-Latin fonts? >> > > More or less, yes. Note that you still need to specify the font-family, but > you could do something like: > > <block font-family="Helvetica,Uming"> > ... > </block> > > In FOP Trunk, if there are any words in the block that cannot be fully > mapped to glyphs in the 'Helvetica' family, then FOP will try 'SimSun' too. > FOP 0.95 only looks at the first family specified in the list. > > > HTH! > > > Andreas > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sam Fuqua ΣΝ ΘΗ 454
