You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Andreas Lehmkühler (Resolved JIRA)" <ji...@apache.org> on 2011/11/01 17:57:32 UTC

[jira] [Resolved] (PDFBOX-1085) Wrong PostcriptScriptTable due to wrong assumption in Encoding/MacRomanEncoding

     [ https://issues.apache.org/jira/browse/PDFBOX-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Lehmkühler resolved PDFBOX-1085.
----------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0
         Assignee: Andreas Lehmkühler

I added the patch in revision 1196127 as proposed by Wulf.

Thanks for the contribution!
                
> Wrong PostcriptScriptTable due to wrong assumption in Encoding/MacRomanEncoding
> -------------------------------------------------------------------------------
>
>                 Key: PDFBOX-1085
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-1085
>             Project: PDFBox
>          Issue Type: Bug
>          Components: FontBox
>    Affects Versions: 1.6.0
>            Reporter: Wulf Berschin
>            Assignee: Andreas Lehmkühler
>             Fix For: 1.7.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When parsing a PostScriptTable of a TrueType font (Format 2.0: Non-Standard (for PostScript) TrueType Glyph Set.) I wondered about the many wrong "space" entries for non-whitespace-glyphs for which TTFDump stated ".notdef".
> I found out that org.apache.fontbox.encoding.(MacRoman)Encoding.getName() puts a "space" when codeToName doesnt find a name.
> This method should be changed to return ".notdef" for unknown codes (means code with no PSGlyf Name)
>     public String getName( int code ) throws IOException
>     {
>         String name = codeToName.get( code );
>         if( name == null )
>         {
>             name = ".notdef";
>         }
>         return name;
>     }

--
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