[texworks] Mac OS TeXworks + fontconfig

Charlie Sharpsteen chuck at sharpsteen.net
Tue Jun 7 19:59:55 CEST 2011

On Tue, Jun 7, 2011 at 7:27 AM, Stefan Löffler <st.loeffler at gmail.com> wrote:
> I guess the last remaining issue that plagues (sort of) the Mac build of Poppler are the .notdef glyphs that show up in the Symbol font:
> One on Snow Leopard:
>     http://i.imgur.com/m0BCk.png
> Two on Leopard:
>     http://i.imgur.com/LEBbh.png
> I don't know if it is really worth hunting these down and eliminating them as TeXworks is not a general-purpose PDF viewer.  It might help with getting patches accepted upstream, but these issues are present in the Fontconfig build as well so we're not really upsetting the status quo by leaving them alone.
> I'm inclined to close this matter. If Apple changes font encodings between releases (it's not even the same glyphs that are .notdef'ed!) we can't help it. Besides, as I pointed out before, TeX documents normally have their fonts embedded, AFAIK. Fixing this would probably need some digging through the encoding tables and adding OS version switches there (though I'm not even sure if it's (easily) possible to have a conditional compilation depending on the OS version...).

I'm not too fired up about fixing this either.

> Speaking of upstream: how do we go about submitting the patches? If you want, I guess it's best if you would submit the patches, as you have all the relevant data (what was broken where, ...) and can answer any questions that may arise. If not, I could submit them as well, of course, but it would be a lot like "here you are, do with it what you want" ;).
> Cheers,
> Stefan

I think we should do the following:

1. Merge the updates to `poppler-mac-font-handling.patch` and the new
`poppler-bogus-memory-allocation-fix.patch` back into the TeXworks SVN
repository. I have exported these patches and attached them to the end
of this email.

2. I'll roll up a new 0.5.0 release that uses Quartz instead of
Fontconfig. That way when we submit the patches back to Poppler, we
can say "X people tried it on Snow Leopard, Y people on Leopard, and
it didn't blow their computers up".

3. Re-submit the patches for inclusion in the Poppler source if there
are no issues with the 0.5.0 build. Perhaps we could also consider
downgrading the changes to the buildsystem so that Fontconfig is stil
the default, but "mac" is now an option.  This would be a smaller
change to the Poppler status quo which might help the patches get

Jonathan, any thoughts on trying another submission to Poppler?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Add-ZapfDingbats-PostScript-name-as-a-special-case.patch
Type: application/octet-stream
Size: 2307 bytes
Desc: not available
URL: <http://tug.org/pipermail/texworks/attachments/20110607/5d2ddf79/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Add-Mac-font-handling-to-Poppler-CMake-buildsystem.patch
Type: application/octet-stream
Size: 3477 bytes
Desc: not available
URL: <http://tug.org/pipermail/texworks/attachments/20110607/5d2ddf79/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0003-Add-patch-to-fix-memory-allocation-for-Splash-Glyphs.patch
Type: application/octet-stream
Size: 1298 bytes
Desc: not available
URL: <http://tug.org/pipermail/texworks/attachments/20110607/5d2ddf79/attachment-0005.obj>

More information about the texworks mailing list