[
https://issues.apache.org/jira/browse/PDFBOX-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141527#comment-14141527
]
Maruan Sahyoun commented on PDFBOX-2333:
----------------------------------------
[~jahewson] Thx for the hint. I know about TextLayout. At that point in time
I’m still looking at the issues we currently have and report these so we get a
complete picture. I’m also creating several documents filling them out using
other software and analyzing the results so we are able to resemble that and
have a testbed as a result.
Although TextLayout (and LineBreakMeasurer) look very promising there are some
potential show stoppers (which we have to evaluate/consider)
- it’s not available on Android
- you need to pass a font (and we already have our experiences using awt fonts)
As a base there are also Bidi, BreakIterator and ICU Classes available which we
could combine with our own font information such as .getStringWidth() to
compute the length of text.
Of course there is still the Identity.H Identity.V 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)
