You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pdfbox.apache.org by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org> on 2012/01/04 13:09:38 UTC

[jira] [Commented] (PDFBOX-605) Better support for Type0 fonts

    [ https://issues.apache.org/jira/browse/PDFBOX-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179434#comment-13179434 ] 

Jukka Zitting commented on PDFBOX-605:
--------------------------------------

The code from revision 1056721 was producing gibberish output for an embedded Type0 font in a document that I unfortunately can't share as a test case. The output is fine if the font is instead accessed as an external system font (i.e. it doesn't go through PDType1CFont.getawtFont()), so in revision 1227129 I changed the logic in PDCIDFontType0Font.getawtFont() to use a system font with the same name by default, and only fall back to the embedded font if the system font is not available.
                
> Better support for Type0 fonts
> ------------------------------
>
>                 Key: PDFBOX-605
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-605
>             Project: PDFBox
>          Issue Type: Improvement
>          Components: PDModel
>            Reporter: Jukka Zitting
>
> Currently the PDType0Font.drawString() method simply falls back to PDType1Font.drawString() and logs an info message about the missing Type0 font support.
> It's better to have such known issues in the bug tracker instead of in log files, so I'm creating this issue to track Type0 support and will remove the log message that just repeats over and over again when dealing with PDF documents with Type0 fonts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira