Bug 103245 - Inserted form text not shown for some (not fully standard-compliant) PDF files
Summary: Inserted form text not shown for some (not fully standard-compliant) PDF files
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-12 17:02 UTC by Michael Weghorn
Modified: 2018-04-11 15:41 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
first sample form (80.15 KB, application/pdf)
2017-10-12 17:02 UTC, Michael Weghorn
Details
second sample form (252.84 KB, application/pdf)
2017-10-12 17:02 UTC, Michael Weghorn
Details

Description Michael Weghorn 2017-10-12 17:02:10 UTC
Created attachment 134815 [details]
first sample form

For some PDF forms, text inserted into text form fields is not rendered at all. I am attaching two sample files. The text is shown correctly when using for example Adobe Reader to fill the forms.

Steps to reproduce:

1) open sample file with Okular or Evince
2) insert text into form field (e.g. "Startbahnhof" in first file, "Vorname und Nachname" in the second sample file)
3) switch to next field

Result:

The inserted text is no longer shown. It also does not show in a printout.

Expected result:

The text inserted into the form value is shown and is also present in a printout.


Note: The original bug report was filed against Okular: https://bugs.kde.org/show_bug.cgi?id=331697
That bug report contains more information and an analysis of what is malformed in the two PDF files as far as I can see.

It was suggested there that a bug against Poppler be opened instead so that the handling of such files can be improved.
Comment 1 Michael Weghorn 2017-10-12 17:02:37 UTC
Created attachment 134816 [details]
second sample form
Comment 3 Michael Weghorn 2018-04-10 13:06:10 UTC
(In reply to Albert Astals Cid from comment #2)
> Fixed
> 
> https://cgit.freedesktop.org/poppler/poppler/commit/
> ?id=8821c04f36cb737776cd9077a46f1a9f86ca54e7

Thanks, Albert!

I did a quick retest with Poppler's current master branch (as of commit 8c8c0034).
The second sample form works nicely now.
However, the first sample form (which has a different root cause) still shows the same problem.

Should I open a separate bug report for that one?
Comment 4 Michael Weghorn 2018-04-11 07:56:50 UTC
(In reply to Michael Weghorn from comment #3)
> (In reply to Albert Astals Cid from comment #2)
> > Fixed
> > 
> > https://cgit.freedesktop.org/poppler/poppler/commit/
> > ?id=8821c04f36cb737776cd9077a46f1a9f86ca54e7
> 
> Thanks, Albert!
> 
> I did a quick retest with Poppler's current master branch (as of commit
> 8c8c0034).
> The second sample form works nicely now.
> However, the first sample form (which has a different root cause) still
> shows the same problem.
> 
> Should I open a separate bug report for that one?

@Albert: Sorry, I had forgotten to add you in CC with my previous comment, so not sure whether you actually noticed it (s. above).

Should I create another bug report for the document that's not working yet?
Comment 5 Albert Astals Cid 2018-04-11 13:09:36 UTC
No need to CC me i see all poppler bugs.

Can you please try again? With poppler master and okular master (okular shouldn't really matter) I get it to work as shown in https://www.youtube.com/watch?v=zIPUjqR68q8
Comment 6 Michael Weghorn 2018-04-11 15:41:05 UTC
(In reply to Albert Astals Cid from comment #5)
> [...]
> Can you please try again? With poppler master and okular master (okular
> shouldn't really matter) I get it to work as shown in
> https://www.youtube.com/watch?v=zIPUjqR68q8

Sorry for the noise! I just tried again and it does actually work; no idea what I did wrong yesterday...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.