[ 
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308287#comment-14308287
 ] 

John Hewson commented on PDFBOX-2661:
-------------------------------------

The font in your rendering is Arial, which is Acrobat's usual substitution for 
Helvetica on platforms which don't have a native Helvetica font.

{quote}
Another weird thing is that if I leave the field in Reader the text goes away 
for "Foobar" and "FranklinGothic-MediumItalic" but not "MinionPro-Bold" or 
"Helvetica-BoldOblique".
{quote}

I noticed this too, it might be an Acrobat bug.

{quote}
I think Adobe Readers knowledge about these fonts are table based...
{quote}

It's possible, but we haven't seen any evidence yet that shows Acrobat doing 
anything beyond looking at the words "Medium" and "Italic" at the end of font 
names, which is a substitution mechanism which we already support in 
ExternalFonts.

{quote}
If you dump the AcroForm.api plug-in binary you'll find that it contains the 
names of hundreds of fonts 
{quote}

That's interesting though there may be other purposes for that least. We need 
to have a PDF which shows fonts with the same name endings e.g. -MediumItalic 
being mapped to different fonts to show that this is actually the case. Can you 
attach a text file with the list of fonts which you extracted from AcroForm.api?

> 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: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Reply via email to