[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308614#comment-14308614
]
John Hewson commented on PDFBOX-2661:
-------------------------------------
Sorry, I was looking at the second line in your rendering when I mentioned
Arial, the first line is indeed Franklin Gothic, which makes sense as you have
it installed. The second "Helvetica" line is Arial. That all makes sense.
My suspicion is that Acrobat isn't using a list of known fonts for text field
substitution and is simply using the PostScript names of the fonts (which are
in the 'name' table in the TTF files). But I'm open to the idea, if we can show
that a substitution exists which could only be performed via a lookup.
Implementing more general mechanisms is always better, as they have proven to
be more robust in practice.
> Implement font fallback for AcroForms
> -------------------------------------
>
> Key: PDFBOX-2661
> URL: https://issues.apache.org/jira/browse/PDFBOX-2661
> Project: PDFBox
> Issue Type: Improvement
> Components: AcroForm
> Affects Versions: 1.8.8, 2.0.0
> Reporter: Maruan Sahyoun
> Fix For: 2.1.0
>
> Attachments: FontTest.java, Fonts.pdf, Fonts2-Filled.pdf, Fonts2.pdf,
> Franklin.png, field-filled.png, field.png, fonts2-filled.png
>
>
> There are forms where the font specified in the fields default appearance is
> not pointing to the correct fields or forms resources entry. Adobe
> Reader/Acrobat have a (unspecified) fallback mechanism to resolve such
> missing fonts.
> We should be ably to come up with a similar solution.
> A sample of such an issue can be found in PDFBOX-1234
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
