Works for me. The problem indicator is in the warning you posted:
it says "SingleByteFont". So I assume you generated an XML font metrics
file with the "-enc ansi" option and use that. But the WinAnsi encoding
does indeed not have these glyphs even through the font itself has them.
So you need to switch to the normal MultiByte TrueType mode. I don't
remember what FOP version you're using but if I do:
<font embed-url="C:/Windows/Fonts/Verdana.ttf">
<font-triplet name="Verdana" style="normal" weight="normal"/>
</font>
it works fine under FOP 0.94 without an XML font metrics file. It's
probably better to use 0.95beta if you don't hit any of the bugs that
have been fixed in the 0.95 branch. That way you can profit from a much
improved font subsystem and do font auto-detection.
On 30.07.2008 10:50:06 Jean-François El Fouly wrote:
> Jeremias Maerki a écrit :
> >
> > No, the mapping is correct. You think in terms of one-byte encodings.
> > XSL-FO and therefore FOP is a Unicode application. If you want the
> > "theta" character (0x03B8, GREEK SMALL LETTER THETA) you need to put the
> > 0x03B8 character in your XSL-FO file. 0x71 always represents a "q" for
> > which the Symbol font doesn't have a glyph and therefore renders as "#".
> >
> Now I see it's high time for me to take a break :-(
> Of course it works, it didn't work because I had been stupid enough (or
> just too tired) to look at the mappings in the MS Windows Symbol font
> instead of using The Unicode Standard though it is on my desk. So
>  and  (I was looking for delta's) go nowhere.
>
> Now if I dare ask a second question about the other problem in my test
> sheet...
>
> <para>Plus petit ou égal (Unicode 2264, LESS-THAN OR EQUAL): ≤</para>
> <para>Plus grand ou égal (Unicode 2265, GREATER-THAN OR EQUAL):
> ≥</para>
>
> renders the symbol as #, with the following warnings in the logs:
>
> 2008-07-30 10:32:21,155 WARN [org.apache.fop.fonts.SingleByteFont] Glyph
> 8804 (0x2264, lessequal) not available in font Verdana
> 2008-07-30 10:32:21,157 WARN [org.apache.fop.fonts.SingleByteFont] Glyph
> 8805 (0x2265, greaterequal) not available in font Verdana
>
> Now the Verdana font that is used on the server has glyphs for the
> Unicode characters above (checked with TypeTool).
> And these are the correct character codes (this time I double checked
> against the book).
> So what did I miss ?
>
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
