[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307812#comment-14307812
]
John Hewson edited comment on PDFBOX-2661 at 2/5/15 7:25 PM:
-------------------------------------------------------------
Reopening, I found out what was happening. Acrobat Pro was modifying the PDF in
real time as I was typing into the form, so without even saving the PDF the
“Internal Structure” view had been updated with all of the missing resources
replaced by Acrobat.
So instead of seeing the original field:
!field.png!
I was seeing the field once it had been filled by Acrobat:
!field-filled.png!
Apologies for the confusion.
was (Author: jahewson):
Reopening, I found out what was happening. Acrobat Pro was modifying the PDF in
real time as I was typing into the form, so without even saving the PDF the
“Internal Structure” view had been updated with all of the missing resources
replaced by Acrobat.
> 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, field-filled.png, field.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]
