[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306887#comment-14306887
]
Maruan Sahyoun commented on PDFBOX-2661:
----------------------------------------
That is not related to fontbox at all (and there is no mention that it should
have anything to do with it).
A field has (maybe inherited) a default appearance which shall at least specify
a font and it's size. The font is a COSName mapping to an entry in the fields
or forms DR font map with that same name. Although the spec required that there
has to be a DR font resource with that same name reality shows that this is not
always the case. The 'font fallback' which the issue is about shall deal with
that situation. All the rest are details.
I'd propose that we agree that there is such handling to be implemented and
look at it after 2.0. That's why I originally hat set the issue to be resolved
in 2.1.
> 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
> Attachments: FontTest.java, Fonts.pdf
>
>
> 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]
