[texworks] Mac OS TeXworks + fontconfig

Stefan Löffler st.loeffler at gmail.com
Fri Jun 3 12:31:49 CEST 2011

Hi again,

On 2011-06-02 18:19, Charlie Sharpsteen wrote:
> Allright, I did some poking around:
>   - Changing ZapfDingbats to ZapfDingbatsITC in base-14-font.pdf does
> not solve the Bogus memory allocation errors, however it does cause
> all the dingbat glyphs to be replaced with .notdef boxes.

I did some searching now. ZapfDingbats is indeed handled specially. From
the looks of poppler/BuiltinFontTables.cc, the glyph widths are
hard-coded, and a special encoding table (see
poppler/FontEncodingTables.cc) is used. Apparently, this is chosen by
Postscript font name.
So, this explains why a font named ZapfDingbatsITC doesn't get the
correct encoding. But since the "Bogus..." messages didn't go away, I'm
beginning to think more and more that there is some peculiarity about
the font file that causes poppler to throw these messages. Maybe some
header field is empty or missing that poppler would expect?

>   - Changing Helvitical to HelviticaFoo and altering the ZapfDingbat
> substitution to operate on it instead had no effect.

No effect meaning that the "Bogus..." messages didn't change, right? So
they are still coming form ZapfDingbats, not from the replaced Helvetica?

>   - I followed the function calls out of GlobalParamsMac.cc and into
> SplashOutputDev.cc.  They don't occur in
> `SplashOutputDev::doUpdateFont` which is the function that calls
> `getDisplayFont` from GlobalParamsMac.cc.
> Not sure what else to do at this point.

Hm, I wonder... The "Bogus..." messages always occur after all "Lookup
font..." messages right? This might suggest that they occur not in the
initialization phase but in the actual drawing phase (possibly in


More information about the texworks mailing list