Thank you, Pascal, for the further explanation, and Medhi for your hint not to use the metrics files.
It turns out that when I use FOP 1.0 directly with the DejaVu fonts and without the generated metrics files, the glyph does appear in the PDF. Regards, Mark On Oct 7, 2011, at 9:24 AM, Pascal Sancho wrote: > Hi Mark, > > font metrics purpose is only when you don't want to embed a font in PDF. > this makes sense with widely distributed fonts, that usually carry a > little set of glyphes. > > For embedded fonts, as said Mehdi, this feature is deprecated. > > See [1]. > > That said, it remains possible that you are facing to a metrics issue, > witch can be caused either during file generation, or at FOP runtime. > Typically, a TTF font without CMAP table are not managed correcly when > using TTFReader (see [2]). > > [1] http://xmlgraphics.apache.org/fop/1.0/fonts.html#custom > [2] http://xmlgraphics.apache.org/fop/1.0/fonts.html#truetype-metrics > > Le 06/10/2011 22:39, Mark Craig a écrit : >> Thank you, Mehdi. >> >> Yes, FOP 1.0. >> >> Does generation of the metrics XML file somehow mislead FOP, then? >> >> Regards, >> Mark >> >> On Thu, Oct 6, 2011 at 10:13 PM, mehdi houshmand <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi Mark, >> >> What version of FOP are you using? In FOP 1.0+ the metrics XML files >> are deprecated. >> >> Mehdi >> >> On 6 October 2011 20:39, Mark Craig <[email protected] >> <mailto:[email protected]>> wrote: >>> Hello, >>> I've read >> http://xmlgraphics.apache.org/fop/faq.html#pdf-characters and >>> http://xmlgraphics.apache.org/fop/1.0/fonts.html#missing-glyphs. >> They seem >>> to suggest that if the font contains a glyph it ought to be >> picked up. >>> I'm using the DejaVu fonts. A ć (c with acute accent, lower case) >> is missing >>> in the PDF, following this warning during generation: >>> Oct 6, 2011 8:23:59 PM org.apache.fop.events.LoggingEventListener >>> processEvent >>> WARNING: Glyph "?" (0x107, cacute) not available in font >>> "DejaVuSansCondensed-Bold". >>> The ć does show up in the UTF-8 encoded .fo. It comes out fine in >> the RTF, >>> which is generated from an identical .fo. >>> I do see ć in DejaVuSansCondensed-Bold in my font viewer. (The >> glyph appears >>> in SansMono on their home >> page, http://dejavu-fonts.org/wiki/Main_Page.) >>> The DejaVuSansCondensed-Bold-metrics.xml file seemed to be >> generated without >>> incident: >>> INFO: Reading >>> >> >> /Users/mark/Documents/workspace/opendj3/src/fonts/DejaVuSansCondensed-Bold.ttf... >>> Oct 6, 2011 8:22:57 PM org.apache.fop.fonts.apps.TTFReader loadTTF >>> INFO: Font Family: [DejaVu Sans Condensed, DejaVu Sans] >>> Oct 6, 2011 8:22:57 PM org.apache.fop.fonts.apps.TTFReader >> constructFontXML >>> INFO: Creating xml font file... >>> Oct 6, 2011 8:22:57 PM org.apache.fop.fonts.apps.AbstractFontReader >>> writeFontXML >>> INFO: Writing xml font file >>> >> >> /Users/mark/Documents/workspace/opendj3/target/fonts/DejaVuSansCondensed-Bold-metrics.xml... >>> Why is the ć missing from the PDF output? >>> Thanks for your time and your help. >>> Regards, >>> Mark >>> > > -- > Pascal > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
