Hi All
I am trying to merge some pdfs together for proofing, then split them back afterwards and thought it would be good to add a bookmark of the filename on each file then merge them and afterwards use the split PDF pages tool to split using the bookmarks. When using the merge tool in Switch though the bookmarks are lost unlike combining the PDFs in Acrobat where the bookmarks are kept. Is there no way in Switch to merge PDFs together and keep the bookmarks?
Thanks
Merge PDFs and Bookmarks
Re: Merge PDFs and Bookmarks
It's simpler if you keep them as they are before the merge for proofing.
The PDF for proofing is just then a copy of the working files.
The PDF for proofing is just then a copy of the working files.
-
billy.olvestad
- Member
- Posts: 62
- Joined: Mon Nov 19, 2018 10:08 pm
- Location: Sweden
- Contact:
Re: Merge PDFs and Bookmarks
Are you using Enfocus Review for proofing?
I would then strongly suggest you submit them as a "job collection" as separate files.
I have a customer that used to merge the PDF files before proofing, and it caused problems. For one thing, if the customer rejected the proof because of one of the files, all the files had to be uploaded again, even though the rest of them were ok.
As a job collection, the jobs are grouped in one interface, but will still be approved separately.
If you absolutely have to merge them, I can tell you how we used to do it.
We gave the jobs a common unique identifier as private data, and saved copies of them in a repository folder, in a subfolder named after the identifier.
We then merged the files and sent it for proof.
When the file came back, we picked up the folder from the repository based on the identifier, and unpacked the folder to send the different files on to their respective destination.
In other words, the files are saved before, and the file that comes back from proof is discarded, and the original files before the merge is sent on.
I would then strongly suggest you submit them as a "job collection" as separate files.
I have a customer that used to merge the PDF files before proofing, and it caused problems. For one thing, if the customer rejected the proof because of one of the files, all the files had to be uploaded again, even though the rest of them were ok.
As a job collection, the jobs are grouped in one interface, but will still be approved separately.
If you absolutely have to merge them, I can tell you how we used to do it.
We gave the jobs a common unique identifier as private data, and saved copies of them in a repository folder, in a subfolder named after the identifier.
We then merged the files and sent it for proof.
When the file came back, we picked up the folder from the repository based on the identifier, and unpacked the folder to send the different files on to their respective destination.
In other words, the files are saved before, and the file that comes back from proof is discarded, and the original files before the merge is sent on.