[poppler] ZapfDingbats cannot be found on Windows

[William Bader]

> whose responsibility should that be -- the poppler library, the client application that uses poppler, or the individual end user?


The final responsibility should be the end user because poppler, ghostscript, and probably many other packages use those fonts, so distributions typically create a package for the fonts instead of including all of the fonts with each application that might use them.

For example, on Fedora 25, the package urw-fonts-3:2.4-22.fc24.noarch provides /usr/share/fonts/default/Type1/d050000l.pfb

Packages that require the fonts probably list urw-fonts as a dependency, so installing ghostscript or poppler-based applications automatically installs the fonts.

So if you install a package from a distribution, the package maintainer has the responsibility to list the fonts as a dependency, while if you build a package from source, you have the responsibility to install all of the dependencies.

>FYI here is the implementation from pdf.js

Most of that code is just setting up an encoding. It looks like the font is coming from an external file.

Regards, William

________________________________
From: poppler <poppler-bounces at lists.freedesktop.org> on behalf of Jeroen Ooms <jeroen at berkeley.edu>
Sent: Wednesday, September 6, 2017 5:05 AM
To: Jonathan Kew
Cc: Albert Astals Cid; poppler at lists.freedesktop.org
Subject: Re: [poppler] ZapfDingbats cannot be found on Windows

On Wed, Sep 6, 2017 at 9:10 AM, Jonathan Kew <jfkthame at gmail.com> wrote:
> On 05/09/2017 21:03, Albert Astals Cid wrote:
>>
>> ./GlobalParamsWin.cc:102:    {"ZapfDingbats",          "d050000l.pfb",
>> "wingding.ttf", gTrue},
>>
>> This is the substitution table, i guess those files are not available on a
>> moderm Windows?
>
>
> I expect wingding.ttf is normally available; but it isn't a suitable
> substitute for ZapfDingbats, as it has a totally different repertoire of
> symbols.
>
> The solution would be to ensure d050000l.pfb is available, but whose
> responsibility should that be -- the poppler library, the client application
> that uses poppler, or the individual end user?

How do other pdf readers solve this? The same pdf renders OK using
e.g. chrome and or firefox on the same machine.

FYI here is the implementation from pdf.js:
https://github.com/mozilla/pdf.js/pull/5251/files
[https://avatars2.githubusercontent.com/u/2692120?v=4&s=400]<https://github.com/mozilla/pdf.js/pull/5251/files>

Add basic support for ZapfDingbats by Snuffleupagus · Pull ...<https://github.com/mozilla/pdf.js/pull/5251/files>
github.com
pdf.js - PDF Reader in JavaScript



_______________________________________________
poppler mailing list
poppler at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/poppler
poppler Info Page - freedesktop.org<https://lists.freedesktop.org/mailman/listinfo/poppler>
lists.freedesktop.org
Subscribing to poppler: Subscribe to poppler by filling out the following form. Use of all freedesktop.org lists is subject to our Code of ...



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/poppler/attachments/20170906/c9e6ddaf/attachment.html>