[
https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308025#comment-14308025
]
Christer Palm commented on PDFBOX-2661:
---------------------------------------
OK, that pretty much confirms my list of mappings.
However, the Asian font mappings on your list looks messed up:
- Does KaMi map to KozMinPro or HeiseiMin-W3? I think it should actually be
KanjiMincho.
- Does HySm map to HYSMyeongJoStd-Medium or HYSMyeongJo-Medium? I think it
should actually be HYSMyeongJo (not -Medium).
- Does STSo map to STSongStd-Light or STSong-Light?
etc...
So those mappings should IMO be confirmed before implemented.
While you're at it with Acrobat Pro, I attached a Fonts2.pdf with references to
"Foobar", "MinionPro-Bold" and "FranklinGothic-MediumItalic". I'm curious to
see what resources Acrobat creates for those fields. Specifically, I'd like to
see if Acrobat maps Foobar to Helvetica straight away or if it maps literally
to Foobar and the fallback happens in the rendering process.
"MinionPro-Bold" and "FranklinGothic-MediumItalic" are known internally to
Adobe Reader, and on my box they get substituted with something not Helvetica
even though I don't have those particular fonts installed (or are they built
into Reader?). It would again be interesting to see if that substitution
happens when creating the appearance stream or if it happens later.
> 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, Fonts2.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: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
