[Bugs] #2541 UNSP: Read can't save a PDF with a form
Sugar Labs Bugs
bugtracker-noreply at sugarlabs.org
Fri Feb 25 05:25:28 EST 2011
#2541: Read can't save a PDF with a form
------------------------------------------+---------------------------------
Reporter: godiard | Owner: godiard
Type: defect | Status: assigned
Priority: Unspecified by Maintainer | Milestone: Unspecified by Release Team
Component: Read | Version: Git as of bugdate
Severity: Unspecified | Keywords:
Status_field: New | Distribution:
Seeta_dev: |
------------------------------------------+---------------------------------
Changes (by sascha_silbe):
* status: new => assigned
* cc: sascha_silbe (added)
* version: Unspecified => Git as of bugdate
* milestone: 0.84 => Unspecified by Release Team
* owner: sayamindu => godiard
* distribution: Unspecified =>
Comment:
This is a limitation of PDF that we'd need to work around by
1. saving the entered values as part of the metadata (=> not preserved
outside of Sugar) and
1. saving a permanently modified version.
1. requires upstream (i.e. [http://library.gnome.org/devel/libevview/
libevview]) support first.
2. would need to be an explicit user action since the original document
wouldn't be recoverable from the filled-out version. But unlike 1. it can
be implemented using the current evince API: by "printing" to a file.
Note that at least evince 2.30.2 has a bug that causes it to not render
fields that have been filled out, but not "left" (by clicking on a
different part of the document) before printing. We might need to work
around this in Read.
In theory 1. would be an enhancement, but since not
[http://wiki.sugarlabs.org/go/Human_Interface_Guidelines#The_Notion_of_.22Keeping.22
preserving changes across Stop/resume] is violating the HIG I'll leave it
marked as defect.
--
Ticket URL: <http://bugs.sugarlabs.org/ticket/2541#comment:1>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list