[
https://issues.apache.org/jira/browse/PDFBOX-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091847#comment-14091847
]
Maruan Sahyoun commented on PDFBOX-2249:
----------------------------------------
There are two ways to deal with appearances (the visual representation of the
form fields) for form fields. One is to generate them when filling the form
(default) the other is to tell the viewing application that the appearances
need to be generated. The benefit of the first one is that the forms appearance
represents the forms data the benefit of the second option is that forms
filling is faster as the appearances doesn’t have to be generated. When the
viewing application generates the appearance the forms content (not the data)
changes and as the result the documents needs to be saved again. Not all
applications respect the form fields appearance i.e. they might choose to
display the fields differently!
That was the reason behind my question which application you are using for
viewing.
> Listbox controls render incorrectly
> -----------------------------------
>
> Key: PDFBOX-2249
> URL: https://issues.apache.org/jira/browse/PDFBOX-2249
> Project: PDFBox
> Issue Type: Bug
> Components: AcroForm
> Affects Versions: 1.8.6
> Environment: Windows 7
> Reporter: John McDonald
> Assignee: Maruan Sahyoun
> Labels: Appearance
> Fix For: 1.8.7
>
> Attachments: JMACTest.pdf, JMAC_PDFBOX_out.pdf, PDFBoxUtil.java,
> PDFFormFields.pdf
>
>
> I have a form with a listbox. I update the value in the listbox using the
> following code:
> PDChoiceField c = (PDChoiceField)f;
> ((PDChoiceField)f).setValue("2");
> I have a combo box that uses the same choices, and it works fine. The issue
> has to do with the rendering of the field. The update of the value (i.e.
> setValue method) works fine, but when I look at the resulting output PDF the
> choices have become unreadable because the font has gone way large.
> I have searched the mailing list, and posted a question regarding this that
> no one has answered, so I am now assuming this is an unknown bug.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.2#6252)
