[ https://issues.apache.org/jira/browse/PDFBOX-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309884#comment-14309884 ]
John Hewson edited comment on PDFBOX-2661 at 2/6/15 8:49 PM: ------------------------------------------------------------- Thanks, Table 1 looks like the font substitution mechanism we discussed above. Table 2 looks like a mapping from PostScript font names to full family names, which are usually just used in the user interface, particularly on Windows which groups fonts by family. Some of the binary data matches flags for bold/italic, which would fit with it being used to group fonts by family in the user interface, and then select bold or italic to choose a specific font. So I suspect that Table 2 isn't used for font substitution, though I won't rule it out quite yet without some further experimentation. was (Author: jahewson): Thanks, Table 1 looks like the font substitution mechanism we discussed above. Table 2 looks like a mapping from PostScript font names to full family names, which are usually just used in the user interface, particularly on Windows which groups fonts by family. Some of the binary data matches flags for bold/italic, which would fit with it being used to group fonts by family in the user interface, and then select bold or italic to choose a specific font. So I suspect that Table 2 isn't used for font substitution, though won't rule it out quite yet. > 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, fonttables.txt > > > 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