We do warn about missing glyphs already in FOP Trunk but I'm sure this
can be improved. Here's some sample output:

[WARN ] Glyph "?" (0x223c, similar) not available in font "Helvetica".
[WARN ] Glyph "?" (0x2192, arrowright) not available in font "Helvetica".
[WARN ] Glyph "?" (0x3b1, alpha) not available in font "Helvetica".
[WARN ] Glyph "H" (0x48, H) not available in font "Symbol".
[WARN ] Glyph "e" (0x65, e) not available in font "Symbol".
[WARN ] Glyph "l" (0x6c, l) not available in font "Symbol".
[WARN ] Glyph "o" (0x6f, o) not available in font "Symbol".
[WARN ] Glyph "W" (0x57, W) not available in font "Symbol".
[WARN ] Glyph "r" (0x72, r) not available in font "Symbol".
[WARN ] Glyph "d" (0x64, d) not available in font "Symbol".
[WARN ] Glyph "~" (0x7e, asciitilde) not available in font "Symbol".
[WARN ] Glyph "?" (0x223c, similar) not available in font "ArialMT".

There's even a guard against to many such warnings per font. See
Typeface.java.

On 03.11.2009 21:53:17 J.Pietschmann wrote:
> On 03.11.2009 08:45, bugzi...@apache.org wrote:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=48108
> [Snip]
> 
> Hi Devs,
> 
> I want to get an opinion: Should we start to emit error
> messages if there is no glyph for a character in the current
> font set? Of course, the user shouldn't be drowned in
> essentially the same message over and over again, perhaps
> by deferring the message to the end of processing and trying
> to compressing multiple missing characters to ranges or
> something like "mulitple characters from unicode block
> NNN didn't have a glyph in font ..."
> 
> J.Pietschmann




Jeremias Maerki

Reply via email to