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 2015/05/06 19:44:01 UTC
[jira] [Commented] (PDFBOX-2789) TTF encoding issues
[ https://issues.apache.org/jira/browse/PDFBOX-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531018#comment-14531018 ]
ASF subversion and git services commented on PDFBOX-2789:
---------------------------------------------------------
Commit 1678048 from [~jahewson] in branch 'pdfbox/trunk'
[ https://svn.apache.org/r1678048 ]
PDFBOX-2789: Support for built-in encoding of TTFs (i.e. encoding = null)
> TTF encoding issues
> -------------------
>
> Key: PDFBOX-2789
> URL: https://issues.apache.org/jira/browse/PDFBOX-2789
> Project: PDFBox
> Issue Type: Bug
> Components: PDModel
> Affects Versions: 2.0.0
> Reporter: John Hewson
> Assignee: John Hewson
>
> I've noticed some issues when trying to encode text using embedded TTF fonts (e.g. filling forms). There's a special case where we use the font's built-in encoding via the cmap finding method described in the PDF spec. The problem is that in this special case, we treat the Encoding as null, which breaks some of the assumptions of the encode(...) method.
> The first thing to do is to handle the case for TTF where encoding is null.
> A second idea is to synthesise and Encoding for the TTF, so that a PDTrueType font has a Encoding just like any other font. That's a bit more tricky, but it would be conceptually much cleaner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org