[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308298#comment-14308298
]
John Hewson commented on PDFBOX-2661:
-------------------------------------
That doesn't make much sense, how would Acrobat know that the resource named
"Helvetica" contains the font for the name "Helv"? It would appear to actually
be a case of the font substitution mechanism which Christer just identified
with regards to "FranklinGothic-MediumItalic", where font resources which are
missing are substituted using the name itself. In this case the name is
/Helvetica, so that's a perfect example. I don't think the resource in DR is
every actually being used, the substitution mechanism doesn't need it, because
it already knows about /Helvetica.
> 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]
