On Sun, 21 Sep 2008 15:04:25 +0200, Benjamin Dumke wrote: > 2. You have to be able and willing to dig into the source code. Using a > precompiled version, I could not have worked on this project, as there > where several things I stumbled upon that simply were not working for me, > and that I had to have changed, obviously without waiting for a fix in the > official svn version, if one were to happen at all. So I am using > 1.3.5svn, but I'm using it with some changes applied, including changes in > the hyphenator and the object placement algorithm, as well as additions to > the scripter and the "Move Pages" dialog.
Are these patches available somewhere? > 3. You have to know your other tools to use as well as know a few things > about the PDF standard itself. Scribus (in any version) is not -- nor ever > will (or should!) -- be a one-for-all tool. One great improvement that > entered the svn version a few months ago was the ability to embed > exisiting PDF files into the newly created PDF. Having lots of > advertisements, most of which I receive as PDF files, this possibility is > invaluable. However, while Scribus-created PDFs can usually be trusted, I > cannot trust every single PDF I receive in terms of standards conformance > et cetera. Since Scribus "only" embeds these PDFs as XObjects, anything > that is wrong with the one small PDF is now wrong with the whole document. > Hence I use a combination of Adobe Reader (not free, I know -- except as > in beer --, but still a very important tool), ghostscript, podofo, and > possibly others, to end up with a flawless PDF. Would you please describe it in more detail? Most resources about checking PDFs are about Acrobat, PitStop, PDF-Analyzer, etc. - closed source tools for Windows. Regards, Helge
