Hi.  I’ve reviewed the documentation for the PDFMerger utility located here:  

  https://pdfbox.apache.org/3.0/commandline.html#pdfmerger

And it appears that it only accepts a list of input files on the command line 
with the -i option.  While this is good, I would also like to be able to pass a 
list of file names (one per line), and have the list of files added to a single 
output file specified by the already-existing -o option.

Why?  The number of files I’ll be merging is larger than most UNIX/Linux shell 
environments permit, and file names may be up to 68-characters long 
(64-character string + .pdf), further reducing the number of files I can merge 
within one command.

While I don’t particularly care how this is implemented, other open source 
utilities follow the convention of prefixing an input file name with an ‘at’ 
symbol (‘@‘), or offer a separate option (“-l” / lowercase L) to specify the 
file.

Testing only needs to be basic — before beginning, ensure all files described 
in the list file exist, and optionally test the correctness/compliance of the 
input PDF’s to ensure a defective merged PDF isn’t created, and ensure that the 
input file doesn’t contain more pages than the PDF spec allows for, and 
potentially adding a warning when files that contain incompatible options 
(password protected features such as copying / printing, etc.) are added.

Given that the use case for this is commercial in nature, I’d like to offer a 
bounty for this feature - I’m neutral as to which platform should be used for 
posting / tracking / paying for this — just let me know which one.  I’d prefer 
to work with one of the core maintainers for the project, but other recognized 
contributors are also eligible, my only requirement is that the change is added 
to the main distribution.  I’d also consider making a donation directly to the 
project if that is preferred.

Thanks.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to