[
https://issues.apache.org/jira/browse/PDFBOX-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141550#comment-14141550
]
John Hewson commented on PDFBOX-2333:
-------------------------------------
I wasn't aware that PDFBox worked on Android?
There's no problem using AWT's Font vs PDFont because we can always create an
AWT Font from a PDFont internally, especially for the "standard 14" fonts this
will be easy.
Bidi and BreakIterator are nowhere near what you need to do proper text layout,
especially if you're interested in Thai. ICU is a fairly good option, though we
just removed it as a dependency?
{quote}
Of course there is still the Identity.H Identity.V issue
{quote}
I'm familiar with these CMaps buts what's the issue?
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
