Published July 28, 2013 | https://doi.org/10.59348/6agph-pja34

Determining glyph availability for FOP

Creators & Contributors

I've just spent the past hour grappling with getting FOP to render the Unicode glyph for a checkmark (U+2713) in PDF output from XSL:FO. I thought I'd share a few things I learnt along the way (that make me feel a bit silly for not knowing them already).

The type of errors I was getting were:

Glyph "✓" (0x2713, checkmark) not available in font "Times-Roman".

Some observations after messing around for far too long:

  1. Fop does not support fallback to a secondary font on a character-by-character basis. If you need a glyph to be rendered that isn't present in your font, well, bad luck. (Unless you specifically tweak your XSL:FO document, which isn't viable in my case.)
  2. There is no way, as far as I can see, that you can map a specific character to use a different font.
  3. There is a great resource at fileformat.info that will tell you what fonts support your glyphs.
  4. Just use DejaVu Sans and save yourself a lot of tweaking.

Determining glyph availability for FOP was originally published by Martin Paul Eve at eve.gd: Martin Paul Eve on July 28, 2013.

Files

10.59348_6agph-pja34.pdf

Files (108.0 kB)

Name Size Download all
md5:ab1dba1e1cc306f4e1bd6c6e58eb50ac
108.0 kB Preview Download

Additional details

Description

I've just spent the past hour grappling with getting FOP to render the Unicode glyph for a checkmark (U+2713) in PDF output from XSL:FO. I thought I'd share a few things I learnt along the way (that make me feel a bit silly for not knowing them already). The type of errors I was getting were: Some observations after messing around for far too long: Fop does not support fallback to a secondary font on a character-by-character basis.

Identifiers

GUID
https://doi.org/10.59348/6agph-pja34
URL
https://eve.gd/2013/07/28/determining-glyph-availability-for-fop/

Dates

Issued
2013-07-28T00:00:00Z
Updated
2013-07-28T10:40:34Z