Since the release of PDFsam Basic 4 we had some support requests regarding the application being unusable and starting with a white screen on Windows.
After some investigation we found some tickets on the openjdk bug tracker here, here and few others, we tested the proposed workaround and it seems to have fixed the issue for those users experiencing the white screen.
As you can see on our GitHub release page, as part of our release process we create a
.asc file corresponding to each downloadable package. Files
.asc are ASCII file containing a plain text digital signature of the corresponding package file.
In the next release you’ll find a couple of enhancements to make you more productive with PDFsam.
Run button is set as default so now you can set your parameters and hit the
Enter key to start the task. We added Windows and Ubuntu context menu so you will be able to right click on PDF documents and
Open with or
Send to PDFsam Basic.
some time ago I wrote a post about PDFsam being on Twitter and the repository for version 3 on GitHub. Following the same path and trying to be more social and less grumpy, we added the Facebook page and the Google plus one.
Follow us and stay updated!
I’m finally back on PDFsam, hopefully full time, and I hope I’ll be able to give you some early version of PDFsam v3 soon. First steps taken are the new GitHub repository for the source code (https://github.com/torakiki/pdfsam) and a new Twitter account (https://twitter.com/PDFsamOSS) where I’ll keep you updated on the development status.
few days ago we released a new version of Sejda and its command line interface. This new release has a nice feature regarding outline (bookmarks) handling during a pdf merge task that might be interesting for some of you. When you merge pdf documents, you can now tell Sejda what to do with the documents outlines, it can merge them as well (default behavior), it can discard them reducing the size of the merged pdf document or it can create a completely new outline with one entry for each merged pdf.
This is currently available using the sejda-console but it will also be included in PDFsam v3 and BTW I’m working very hard on the new version of PDFsam, I hope I’ll be able to give you something testable soon.
Hi Mac users,
some of you reported the “PDFsam is damaged and can’t be opened” error when trying to install the PDF Split And Merge dmg package.
After some investigation and users feedback I can finally write what is causing that. The issue is caused by a new feature of Mountain Lion and OS X Lion v10.7.5, called Gatekeeper which “help protect your Mac from malware and misbehaving apps downloaded from the Internet”. It does that by preventing you from launching apps that are not downloaded from the Mac App Store which is “The safest and most reliable place to download and install apps”. Now, assuming you still want to install PDF Split And Merge even if you didn’t download it from the “safest and most reliable place”, what can you do? You have to:
- Open Gatekeeper settings located in “System Preferences > Security & Privacy”
- Set “Allow applications downloaded from:” to “Anywhere” and confirm by pressing “Allow From Anywhere”
- Launch Pdf Split And Merge
- Once PDF Split And Merge is successfully launched, you can set back Gatekeeper option to whatever you want
Some more information can be found here
Hi, here is a simple tip to remind you how page selection works. When merging pdf files you’ll often need to merge only a subset of the document (a chapter, some pages..). PDFsam supports page selection in the form of comma separated values where they can be single pages or page ranges. Page numbers cannot be duplicated and page ranges cannot intersect, a page range with open end is also supported (Ex. 10- means from page ten untill the end of the document). To set the selection on a pdf input document you want to merge, you can double click the page selection cell and input some valid page range.
Examples of valid page selections:
Examples of invalid page selections:
I updated the Wiki adding a simple tutorial on how to modify the amount of memory that PDFsam can use to minimize OutOfMemory errors.
Here is the link.
If, when you double click the pdfsam.exe, an error window shows the message “Cannot find javaw.exe”, it means that it cannot find a working Java installation. To solve this problem try installing (or reinstalling) a working Java Runtime Environment (1.4.2 or above). It can be found here http://www.java.com .