Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 6.3.2
-
Fix Version/s: 6.3.3
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:PRO
-
Support Case References:Support Case 00014441 :- https://icesoft.my.salesforce.com/5000g000023C5AO
Description
A community member has contributed a suggestion for the better handling of the Zapf Dingbats font encoding. We currently rely on the system to have the Ghostscript dingbats font installed to get around the strangeness of the MS Zapf Dingbats font.
Further information from our developer:
Confirmed: document uses Zapf Dingbats font, symbol 0x0034 (see selected text in "String value" window on a screenshot, 0x0034 is '4' in ASCII but mapped to Unicode 0x2714). For reference see https://en.wikipedia.org/wiki/Zapf_Dingbats.
Thus, it is not a bitmap, but a regular symbol.
Mozilla had similar issue with pdf.js and they solved it by using a special Dingbats encoding that converts character 0x0034 to the proper Unicode 0x2714 supported by other fonts if this one is not available (see https://github.com/mozilla/pdf.js/pull/5251/files)
Further information from our developer:
Confirmed: document uses Zapf Dingbats font, symbol 0x0034 (see selected text in "String value" window on a screenshot, 0x0034 is '4' in ASCII but mapped to Unicode 0x2714). For reference see https://en.wikipedia.org/wiki/Zapf_Dingbats.
Thus, it is not a bitmap, but a regular symbol.
Mozilla had similar issue with pdf.js and they solved it by using a special Dingbats encoding that converts character 0x0034 to the proper Unicode 0x2714 supported by other fonts if this one is not available (see https://github.com/mozilla/pdf.js/pull/5251/files)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion