Package: pdftk Followup-For: Bug #421343 Thanks for packaging pdftk !
While I agree that the FDF file format (apparently: ASCII with enclosed BOM-prefixed UTF-16-BE field values) seems rather cumbersome to handle with text oriented tools this does not seem like a bug to me. The UTF-16-BE parts you refer to are not the field *names* but rather the *content*. Content apparently can come encoded as UTF-16-BE as per the PDF spec. Here is how to parse and replace those fields with Python: http://gitorious.org/gnumed/gnumed/blobs/master/gnumed/gnumed/client/business/gmForms.py (look at cPDFForm.substitute_placeholders(), mainly) HTH, Karsten -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (50, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdftk depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib ii libgcc1 1:4.6.0-10 GCC support library ii libgcj12 4.6.0-3 Java runtime library for use with ii libstdc++6 4.6.0-10 The GNU Standard C++ Library v3 pdftk recommends no packages. Versions of packages pdftk suggests: ii poppler-utils [xpdf-utils] 0.12.4-1.2 PDF utilitites (based on libpopple ii xpdf-utils 3.02-12 Transitional package for poppler-u -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org