Merge fails if path to files contains special characters

[bojo42]

Binary package hint: pdfchain

When the parent directory of the PDF files to merge contains white spaces in it's name the underlying pdftk fails with errors like these:

sh: PATH TO/FILE.pdf: not found

Seems like PDF Chain doesn't pass white spaces containing paths correctly to pdftk or pdftk can't handle such path names. It should be noted that white spaces in filenames are working.

[Johann Felix Soden (johfel)]

Thanks for your report. At the moment, only ordinary spaces seems to be handled correctly.
If other white-space characters (like tabs or newlines) are in the path, pdfchain fails, which I can reproduce.
It seems that your path contains at least one newline character. If not, does the path contain some other special character?
Can you check this, please?

[bojo42 (bojo42)]

oops you're right i had some german umlauts in the path name as well. but i thought that shouldn't matter as we're on UTF-8. thanks for your instant reply.

[Martin Singer (mpower3)]

Hi,

yes, that's true. Not every special sign that doesn't work with PDFTK
will be checked (I didn't know them all). At the next release I will
consider this. I'm very sorry. But I haven't time to work on pdfchain at
the moment.

Greetings,
Martin Singer

Am Donnerstag, den 30.09.2010, 14:48 +0000 schrieb Johann Felix Soden:
> Thanks for your report. At the moment, only ordinary spaces seems to be handled correctly.
> If other white-space characters (like tabs or newlines) are in the path, pdfchain fails, which I can reproduce.
> It seems that your path contains at least one newline character. If not, does the path contain some other special character?
> Can you check this, please?
>

[bojo42 (bojo42)]

BTW i haven't found a bugtracker for PDF Chain, could you consider to just use Launchpad -> https://bugs.launchpad.net/pdfchain

Thanks for PDF Chain so far

[mmalmeida (mmalmeida)]

This is a rather critical bug - could the backports be updated with the new version of the tool?

[mmalmeida (mmalmeida)]

Since the issue was fixed upstream, could a package maintainer release an updated version in the backport repositories?