mercredi 21 janvier 2015

PDF forms - keyboard issues


Battling some PDF documents that have forms. pdfinfo yield:



Title: FOO
Subject: BAR
Author: St. Claus
Creator: Acrobat PDFMaker 10.0 for Word
Producer: Adobe PDF Library 10.0
CreationDate: Fri Dec 13 10:11:31 2013
ModDate: The Oct 21 14:13:07 2014
Tagged: yes
UserProperties: no
Suspects: no
Form: AcroForm
JavaScript: yes
Pages: 2
Encrypted: no
Page size: 595.32 x 841.92 pts (A4)
Page rot: 0
File size: 1683801 bytes
Optimized: no
PDF version: 1.6


Tested various PDF readers for filling out the forms. Thus far there are two candidates - but with issues:


Evince


Issue: Usually only one field can be filled by keyboard at a time. After one field is entered the keyboard becomes unresponsive. Even “Save a copy ...” does not give the the possibility to enter a file-name. One “solution” is to have a text editor beside the document and copy text by using the mouse and context menu form right click. This works both for fields and new file-name. Another hack is to save with overwrite for each field. Re-open document, fill next field. Close-save, re-open etc. Not a solution.


It is however responsive for menu keys Alt+F when no field has focus.


CABAReT Stage


Issue: Every key-stroke result in two characters being entered. That is:



A -> AA
l -> ll
...


Have tried modifying repeat sensitivity for keyboard, (as I usually have it at around 150ms), but still the same issue.




Evince would be the preferred application of the two.


As of now I use VirtualBox with Windows XP and run Adobe Acrobat Reader (where the form fills OK). But do not look at that as a solution. Adobe has scrapped support for Linux when it comes to Acrobat Reader, (as they have done with Flash), so there are no install candidates (readily) available for Linux.


Have not tested Ocular (KDE) as I am on Xfce, (daily use – but also have GNOME 3 installed ... urk-mix).


Evince is of version 3.14.1. Had a look at 3.15.x but did not compile it as it depends on GTK+ version above system version etc. But from the NEWS file I can not find any suggestion they have worked on this issue. I might be wrong.


Anyone know what could be going on here? A hack / fix for this issue? Optionally some other reader.



Aucun commentaire:

Enregistrer un commentaire