You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "John Hewson (JIRA)" <ji...@apache.org> on 2014/08/28 21:10:10 UTC

[jira] [Commented] (PDFBOX-2091) Some characters are not rendered (font with symbol encoding)

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

John Hewson commented on PDFBOX-2091:
-------------------------------------

I've just fixed this issue again as part of PDFBOX-2262. The conversation above is mostly incorrect, this file is a valid PDF and rendering it follows the spec exactly. The font _does_ contain the character mappings, but not in it's (3,1) or (1,0) "cmap" tables, instead the PostScript names for glyphs are contained in the "post" table. The PDF spec describes exactly what to do in the fallback situation for nonsymbolic fonts:

{quote}
PDF 32000, p266:
In any of these cases, if the glyph name cannot be mapped as specified, the glyph name shall be looked up in the font program’s “post” table (if one is present) and the associated glyph description shall be used. 
{quote}

I've removed the existing workaround of using the (3, 0) table and replaced it with the mechanism described in the spec.

> Some characters are not rendered (font with symbol encoding)
> ------------------------------------------------------------
>
>                 Key: PDFBOX-2091
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2091
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Rendering
>    Affects Versions: 2.0.0
>            Reporter: Juraj Lonc
>            Assignee: Andreas Lehmkühler
>             Fix For: 2.0.0
>
>         Attachments: PDFBOX-2091_TTFGlyph2D.diff, missing_yaccute.pdf, output.png
>
>
> Some characters are not rendered (see attached PDF).
> In this case it is "yaccute".



--
This message was sent by Atlassian JIRA
(v6.2#6252)