as you know I’m working on v3.0.0 and I’m currently working on the user interface. I created a forum post where I attached some screen, I’d like to discuss the UI with you… after all it’s you who is going to split and merge documents with pdfsam and you are probably the best source of ideas and experience.
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 “most reliable place”, what can you do? As sorice pointed out you have to:
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 till 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 finally found some time to release the new version of pdfsam. I want to apologise for the long delay but, as some of you may know, I worked hard on a couple of other projects (What A Cult and Sejda) in the past year and pdfsam was left a bit behind. Release 3 of pdfsam is not coming out any time soon so I decided to release version 2.2.2 with fixes to some of the most annoying bugs. Among the others:
As usual the new version can be downloaded here.
Please report back if you find any issue.
I just uploaded the Windows MSI installers (32 and 64 bits) for the enhanced version. The installers allow silent and Active Directory installation. Currently only the pdfsam enhanced version has been ported to MSI installer but with the next release (in about a month) pdfsam basic will have it too. Please report if you find any bug.
first of all merry Christmas
I decided to write this post to keep you informed about the plan for the next release of pdfsam. After some thoughts I decided to rewrite pdfsam for the same reasons why me and Eduard developed Sejda completely rewriting the pdfsam-console. Here is a short list of the changes you can expect in the next release:
It’s going to take a while but I hope the final result will be a pleasant surprise for most of you.
great news! After more then one year of development today we released Sejda!
You are probably asking “What the heck is Sejda?”. It’s a PDF manipulation layer written in Java. “uh?”. Ok, as many of you know I’ve been working on pdfsam for 6 years now and I realized at some point that the pdfsam-console (the component providing pdf manipulation capabilities to pdfsam) has some… mm… limitations.
Quoting Sejda FAQ:
I realized at some point that some of the design choices I made were unfortunate and the code base wasen’t inline with 2010 software development standards. Pdfsam itself was/is working pretty well but maintenance was/is a bit of a hell so I made the choice, I started to rewrite the pdf manipulation logic with 5 years of experience on my shoulders and trying to keep a close eye on quality and best practices.
What are the advantages compare to the pdfsam-console?
it has more features, it has a bigger team working on it (we are 2 now), it’s built trying to follow best practices from Joshua Bloch in Effective Java and Robert C. Martin in Clean Code, it’s easier to maintain and extend and it’s not tied to a single pdf manipulation library but it tries to take advantage of strength points of all of them
It’s not going to affect pdfsam in the short period but I’ll start to work on a new pdfsam release using Sejda as manipulation library.
Now you may ask “why should I care NOW then?”. We developed and released a Command Line Interface together with Sejda called sejda-console. It provides a set of commands to manipulate PDF documents using all the features provided by Sejda and for all the ones of you using the pdfsam-console and brave enough to switch to the sejda-console, it may be a good opportunity to try it and give us back some feedback. To make it more interesting I have to say that the sejda-console provides some more functionalities compared to the pdfsam-console:
We really hope to have feedbacks, opinions and suggestions from you, as you always did with pdfsam. You can find a lot of information, download link, javadocs etc at the Sejda webpage.
oh, of course Sejda is free and open source.