Page 3 of 6

Re: PDFMaker 0.2 - help beta test!

Posted: 10 Nov 2010, 15:08
by univurshul
Misty wrote: Do users mind having both ImageMagick and GraphicsMagick installed, or would people prefer to only need one installation even if that means a much slower conversion process?
I personally am about precision-made ebooks, but I also like quick-and-dirty on rare occasion. My belief is if you can produce a well-made ebook, you can then produce compressed/tweaked seeds for various reasons and applications.

I need to study backgrounds and all these nuances before I can comment further.

Re: PDFMaker 0.2 - help beta test!

Posted: 10 Nov 2010, 15:15
by Misty
There's no difference in quality between using ImageMagick only or IM + GraphicsMagick. The only difference is speed (GM is far faster at splitting pages), and that one solution requires users to have both programs installed. (Of course, that will change if GM adds transparency support for PDFs.)

Edit: Should have noted in my previous posts that the IM vs GM question is a separate thought rather than a continuation of my answer to your question. Sorry I was unclear.

Re: PDFMaker 0.2 - help beta test!

Posted: 14 Nov 2010, 10:48
by wendel
Misty,
I'm having a small issue with PDFMaker 0.2. I'm running it under windows and have spaces in one of my directory names. I have the -d directory quoted when starting PDFMaker 0.2.

The error is "Magick: unable to open image 'Scanner\Book\Work....' " which starts just where the space is in the directory "Book Scanner". If I change the directory to "Book_Scanner" it works.

Re: PDFMaker 0.2 - help beta test!

Posted: 15 Nov 2010, 10:23
by Misty
I'll take a look into that. Are you enclosing your directory name in quotes? E.g., -d "F:\Book Scanner\Book\Work" instead of -d F:\Book Scanner\Book Work

Re: PDFMaker 0.2 - help beta test!

Posted: 15 Nov 2010, 10:28
by wendel
Are you enclosing your directory name in quotes? E.g., -d "F:\Book Scanner\Book\Work" instead of -d F:\Book Scanner\Book Work
yes I am.

Re: PDFMaker 0.2 - help beta test!

Posted: 17 Nov 2010, 23:34
by dansheffler
An OSX port of the work so far would be much appreciated by a particular scholar who has an unfortunate combination of mid-level coding experience and hi-level work load. As I understand it jbig2enc and pdf.py can both be compiled on OSX, but I can't seem to get things working.

I was also wondering if this kind of thing could eventually be added into ST as an additional step.

Re: PDFMaker 0.2 - help beta test!

Posted: 18 Nov 2010, 12:13
by Misty
Right now it's written in AutoIt, largely because that happened to be the only programming tool on my work computer when I started. I'm going to be doing a simple Python port soon(ish, work is a bit busy right now), and since OS X has Python you should be good. I have a Mac at home to compile any stuff that needs compiling (e.g. jbig2enc). Is there kind of a consensus that people would rather a quick'n dirty Mac/Linux port now, before OCR gets integrated?

pdf.py has a bug that keeps it from working 100% correctly out of the box, anyway. It's only a demo script, Adam doesn't intend it as something serious for production. PDFMaker's going to be using a modified version to correct that bug.

Adding this to ST is definitely possible, but I don't think that's a priority of Tulon's. If a community fork goes ahead after Tulon retires as he plans, that could happen.

Wendel: I'll upload a fix for that soon. I believed that AutoIt would escape spaces in those circumstances, but apparently it doesn't.

Re: PDFMaker 0.2 - help beta test!

Posted: 18 Nov 2010, 12:43
by Tulon
Misty wrote:If a community fork goes ahead after Tulon retires as he plans, that could happen.
Don't wait for me to completely retire. Do the fork as soon as you've got some code to push into it.

I may still be working on ST from time to time, but I will be doing it just for fun. This means I no longer view this project as a deliverable, but rather as a research playground for myself.

Re: PDFMaker 0.2 - help beta test!

Posted: 24 Nov 2010, 08:52
by JonEP
Misty,

I'm eager to try out PDFMaker. I'm running x64 Windows 7, which presents problems. As far as I can tell, the binary release of ImageMagick just wont install properly (see http://www.imagemagick.org/discourse-se ... =3&t=17303). According to info at that link, all versions of the installer after 6.4 were compiled with Visual Studio 10, which is the source of the error, and earlier versions are available only as "install from source" packages, which require the user to compile them themselves using visual studio ide. This is beyond my abilities as a user, right now. Indeed, I may be completely wrong, and may have misunderstood my own failure to install imagemagick properly (this would not be unusual or unwelcome news). When I attempt an install of ImageMagick, I am able to run the command imdisplay logo.miff that is part of the initial test, and when I then attempt to run pdfmaker -dir "outdir" I get the message 'pdfmaker' is not recognized as an internal or external command...

Thanks for working on this, I'll be interested to see how it goes and hope I can make use of it in the future,
Jon

Re: PDFMaker 0.2 - help beta test!

Posted: 24 Nov 2010, 09:53
by spamsickle
I haven't tried PDFmaker myself, but from what you've described it sounds like you have ImageMagick installed properly, but don't have PDFmaker in your path. Try executing it with the fully-qualified name (i.e., c:\somedirectory\pdfmaker rather than simply pdfmaker).