pdfbox-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Hewson <j...@jahewson.com>
Subject Re: pdfbox warnings
Date Wed, 08 Apr 2015 02:20:39 GMT
I re-opened PDFBOX-1900 and added a new substitute for ZapfDingbats using a font
available on Windows. After some research, I found that neither Windings nor Webdings
are suitable substitutes and instead chose Arial Unicode MS because it provides
coverage for all the ZapfDingbats glyphs via their unicode characters.

This fix will be available in the next 2.0 snapshot build.

— John

> On 7 Apr 2015, at 05:00, Eric Douglas <edouglas@blockhouse.com> wrote:
> On Tue, Apr 7, 2015 at 2:56 AM, John Hewson <john@jahewson.com> wrote:
>> On 6 Apr 2015, at 14:38, Tres Finocchiaro <tres.finocchiaro@gmail.com>
>> wrote:
>>>>> ExternalFonts.addSubstitute("ZapfDingbats", "WingdingsRegular");
>>>>> That will map Zapf Dingbats to Webdings. If it works then we can
>> include
>>>> that substitution by default in PDFBox.
>>> Just a lurker chiming in here... If John Hewson's statement is true,
>>> doesn't the substitution solve this?
>> Yes, we just need to make sure to choose a substitute (Windings,
>> Webdings?) which provides the necessary glyphs (I believe that they're all
>> in Unicode, so our existing cmap mapping mechanism for TTF glyphs should
>> handle it once we map the font name).
> Is that a real solution?  Is Zapfdingbats available on any platform?  Is
> Wingdings available on every platform or free to redistribute?
> I don't know what characters are in Zapfdingbats versus Wingdings, but it
> would need a mapping.  I tested replacing Zapfdingbats with Wingdings in my
> own app yesterday and had to change the character code to print a check
> mark.
>>> I have a custom FontMapping.Properties
>>> <
>> https://github.com/qzindustries/qz-print/blob/1.8-pdfbox/pdfbox_1.8.4_qz/src/org/apache/pdfbox/resources/FontMapping.properties#L21
>>> (github.com) that I use for this stuff because the font replacement on
>>> Linux seems to be lacking for many standard fonts.  If an equivalent
>>> exists, shouldn't the project try to use it?
>> Yes, usually our font mapper handles this automatically but as you've
>> noticed sometimes it's necessary to hard-code some hints.
>>> I personally don't like the idea of copying fonts from an Adobe area
>> into a
>>> systems area, especially as a recommendation for using a Java library.
>>> Something feels wrong about that, personally. :) $0.02
>>> -Tres
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@pdfbox.apache.org
>> For additional commands, e-mail: users-help@pdfbox.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message