pdfbox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tilman Hausherr (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PDFBOX-4471) Different fields look alike if they have the same /AP/N before value change
Date Mon, 25 Feb 2019 19:22:00 GMT

    [ https://issues.apache.org/jira/browse/PDFBOX-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777229#comment-16777229

Tilman Hausherr commented on PDFBOX-4471:

Having handlers for each type would make it easier to find where the real stuff is done, but
it should be taken care not to have double code because insertGeneratedAppearance() does most
of the job for all types.

> Different fields look alike if they have the same /AP/N before value change
> ---------------------------------------------------------------------------
>                 Key: PDFBOX-4471
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4471
>             Project: PDFBox
>          Issue Type: Bug
>          Components: AcroForm
>    Affects Versions: 2.0.13
>            Reporter: Tilman Hausherr
>            Priority: Major
>         Attachments: csOnePage.pdf
> See attached SO answer - in the attached file, different fields point to the same /AP/N
object. I think this could be fixed by changing {{AppearanceGeneratorHelper.setAppearanceValue()}}
by removing the "if" segment in {{if (appearance != null && appearance.isStream())}}
and keep the "else" part only.
> I'm wondering why we are reusing the existing appearance stream, is there are use case
to this? I ran the tests after making the change and there was a difference but it was invisible.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org

View raw message