Il 08/12/2014 00:17, Martin Vaeth ha scritto:
> Michał Górny <mgo...@gentoo.org> wrote:
>> Have you tried mcpdf?
> I heard about it now for the first time.
>
> If I understand correctly, it uses the same library
> as pdfTK, only a somewhat later version
> (e.g. with improved unicode handling).
>
> The main difference seems to be that it does not insist
> on gcj but apparently should work with any java: I had
> suspected that it is the library which depends on some
> gcj internals and not just the front-end which consists
> just of a few lines, anyway.
>
> So, indeed, this looks like it should be a drop-in
> replacement, though I did not check whether the
> license of the updated library changed.
>
> Anyway, it would be nice to have it in the tree. ;)
>
>> but testing with your tricky PDFs
> I do not remember anymore. I just remember that
> several times, when some deadline approached,
> I had to resort to pdftk at my institute's Debian
> (in the lack of a gcj at home), even for simple tasks
> as merging pdftex output with some scanned PDF pages:
> neither pdfjam nor poppler did it satisfactory,
> though I do not remember the reasons.
>
A simple concatenation does not work for me:

$ alias pdftk='java -jar /srv/git/M/mcpdf-0.2.1-jar-with-dependencies.jar'
$ pdftk \
>  4265498/0010-visura_alvise.pdf 4265498/report_sister_AT00.pdf
4265499/0010-visura_alvise.pdf \
>  cat output OUT.pdf
java.lang.RuntimeException: Unknown operation:
4265498/report_sister_AT00.pdf
See README for more information.

also having it in tree would be better, and a pair of warnings:

- The project only has 20 commit, last one 8 months ago
  https://github.com/m-click/mcpdf.git
- in the readme there is this "Note that not all PDFtk operations are
implemented at the moment."

hardly a drop in I would trust to replace pdftk which only had problems
once (at compile time) because of a gcc upgrade.

but
find /g/portage/ -name '*.ebuild' -exec egrep 'sys-devel/gcc.*gcj' {} +
show that really only pdftk, dev-java/ecj-gcj and dev-java/gcj-jdk
depend on gcc with gcj enabled.
maybe too few to maintain a broken gcc extension, probably also "go"
should go

regards,
Francesco Riosa


Reply via email to