[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306860#comment-14306860
]
Maruan Sahyoun commented on PDFBOX-2661:
----------------------------------------
Opening the file in Adobe Reader and filling out the form fields, the various
fonts are respected although there is no resource entry with that name. I don't
think that I need to write what should actually be contained in a field and
forms dictionary, what's missing in that particular case and what Adobe Reader
does as all of that has been done BEFORE opening that ticket. [~cpalm] has been
so kind to generate a reduced test case which reflects the forms in PDFBOX-1234
and PDFBOX-1550 and also shows some of the internal undocumented (wrt the PDF
specification) behave.
The issue is not about the page content stream but about how to generate a
fields appearance stream from the information in the fields and forms
dictionary mainly the DR and DA entries.
> 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: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
