[
https://issues.apache.org/jira/browse/PDFBOX-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14142097#comment-14142097
]
John Hewson commented on PDFBOX-2333:
-------------------------------------
{quote}
There are no such restrictions that only certain fonts can be used within forms
{quote}
Yes, it seems so, though there are certainly fonts which could not be used in
this manner (e.g. embedded CID fonts which us an Identity-H or V encoding lack
the required information to map from Unicode text entered by the user back to
glyphs to be displayed in the font. The only mapping they contain is from PDF
character codes (which are meaningless) directly to glyphs (whose name, in this
case a CID from the Identity-H CMap is meaningless).
{quote}
There are already text layout mechanisms in fop, odftoolkit
{quote}
This sounds really promising - any links to the relevant source code?
> Overhaul the apperance generation for PDF forms
> -----------------------------------------------
>
> Key: PDFBOX-2333
> URL: https://issues.apache.org/jira/browse/PDFBOX-2333
> Project: PDFBox
> Issue Type: Improvement
> Components: AcroForm
> Reporter: Maruan Sahyoun
> Fix For: 2.0.0
>
> Attachments: AcroForms-SimpleTextFields.1.8.7.pdf,
> AcroForms-SimpleTextFields.1.8.7.png, AcroForms-SimpleTextFields.pdf
>
>
> The appearance handling for forms in 1.x is limited and does not reflect all
> settings possible for form fields. In addition the current code is not very
> modular and does not follow the box model used for form fields.
> Unfortunately only the basics of form handling are defined in the PDF spec.
> The details like padding of boxes, text placement etc. have to be determined
> by looking at how Adobe forms are generated.
> Update: The file from PDFBOX-2310 has bad rendering which might be related?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
