[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310781#comment-14310781
]
Christer Palm commented on PDFBOX-2661:
---------------------------------------
{quote}Table 1 looks like the font substitution mechanism we discussed
above.{quote}
It's certainly likely to be part of it since it's the only place where the
shorthand names occur, although the list itself obviously doesn't specify the
actual mapping.
Also, there are 21 short and 28 full names on the list if we include the
mysteriously missing "Courier", so there's gotta be more to it than simply
mapping X to Y that I haven't been able to figure out. We've shown that the
names on the list are not the only names that can be used without a
corresponding pre-existing font resource, so it's not that.
Any ideas?
> 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, fonttables.txt
>
>
> 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]
