You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/06 20:45:28 UTC
[jira] [Commented] (PDFBOX-2317) ZapfDingbats should use its own
glyph list
[ https://issues.apache.org/jira/browse/PDFBOX-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124591#comment-14124591 ]
ASF subversion and git services commented on PDFBOX-2317:
---------------------------------------------------------
Commit 1622903 from [~jahewson] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1622903 ]
PDFBOX-2317: ZapfDingbats uses its own glyph list
> ZapfDingbats should use its own glyph list
> ------------------------------------------
>
> Key: PDFBOX-2317
> URL: https://issues.apache.org/jira/browse/PDFBOX-2317
> Project: PDFBox
> Issue Type: Bug
> Components: PDModel
> Affects Versions: 2.0.0
> Reporter: John Hewson
> Assignee: John Hewson
>
> Rendering the file from PDFBOX-2307-159827 (p2) results in the log message:
> {code}
> WARNING: No Unicode mapping for a73 (1) in font ZapfDingbats
> {code}
> The reason is that Zapf Dingbats doesn't use the Adobe Glyph List, it uses its own special glyph list. This is part of the PDF spec, and the download can be found at http://sourceforge.net/adobe/aglfn/wiki/Home/
> We need to make use of this glyph list specifically for the ZapfDingbats font, the most flexible approach is probably to have GlyphList instances associated with PDFonts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)