Bug 14397

Summary:	evince displays form data in a pdf file incorrectly
Product:	poppler	Reporter:	Sebastien Bacher <seb128>
Component:	general	Assignee:	poppler-bugs <poppler-bugs>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	freedesktop
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	14433
Bug Blocks:

Description Sebastien Bacher 2008-02-06 00:31:33 UTC

The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/184741

"Binary package hint: evince

I was using two different programs to fill a pdf form (Adobe Reader 8.0, allows to save data now, and Cabaret)
Evince shows check-mark in a wrong spot: it shows "Yes" while it is "No".

Attached is the file that has the problem. See page 2, question "B" (Were you ever a U.S. citizen).
Evince shows "Yes", while Adobe reader shows "No"

The form is taken from www.irs.gov (it has public access)

http://launchpadlibrarian.net/11456651/f1040nre-2007.pdf
The file that shows the problem  (303.3 KiB, application/pdf)"

Comment 1 Albert Astals Cid 2008-02-08 15:24:53 UTC

That's because the file uses JavaScript to calculate field values, we don't support JavaScript at the moment

Comment 2 Jean Christophe André 2009-02-09 13:15:23 UTC

I confirm this specific check-mark bug is not present anymore with poppler 0.10.3 using Evince 2.25.5 from Ubuntu "Jaunty".

It has been one year now since this bug has been opened. May be some poppler developer could officially confirm the JavaScript support and close this bug?

Comment 3 Albert Astals Cid 2009-02-09 13:39:54 UTC

i already said we don't support JavaScript, what else do you want?

If you want it fixed come back with something like 60000€ so we can leave our day time works and work on fixing JavaScript on poppler. A patch to make it work is also accepted.

Comment 4 Jean Christophe André 2009-02-09 13:49:12 UTC

(In reply to comment #3)
> i already said we don't support JavaScript, what else do you want?

Ooops… Please don't get mad at me! I was just trying to help!!

May be I misunderstood but you said "we don't support JavaScript _at the moment_" and it was 1 year ago…

And since this bug report's problem *went away* I (wrongly?) supposed it was because poppler's developers (thanks to them) had worked on it!

> If you want it fixed come back with something like 60000€ so we can leave
> our day time works and work on fixing JavaScript on poppler. A patch to
> make it work is also accepted.

I fully understand that: I'm (sometime) a developer too and not paid for what I give as free software (hopefully I've other resources)…

But here I was talking about *closing* this bug… Sorry if I didn't write it correctly, I'm not a native English writer either…

Comment 5 Albert Astals Cid 2009-02-09 14:05:29 UTC

Err, i can't read, you said "is not present", i suck :(

you mean it's fixed? /me checks

Right, that specific problem seems fixed though we never added JavaScript support.

Closing then, thanks for notyfing it's been fixed!

And again sorry for being unable to read.

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.