[ANN] jpeg2pdf v0.1

[Koen Vervloesem]

Hi,

I'm pleased to announce you jpeg2pdf version 0.1.

jpeg2pdf is a free program that converts a directory of JPEG files to a
PDF file.

Features:

* jpeg2pdf is fast. Unlike ImageMagick or other general image
conversion tools, jpeg2pdf is specialized for its task an does this
very efficiently.
* jpeg2pdf generates compact PDF files. Unlike general image
conversion tools, jpeg2pdf doesn't do any processing/rescaling of the
images, nor does it generate thumbnails of the pages in the PDF file.
* jpeg2pdf is cross-platform. It works on any platform the Ruby
programming environment runs on. This includes Windows 95/98/NT/XP,
GNU/Linux, Mac OS X, Solaris, AIX, OS/2 and DOS.
* jpeg2pdf is a command-line program. So it can very easily be
integrated in a shell script or a web server process to automate a
conversion task.
* jpeg2pdf is free. You can download it and use it for free.

Homepage: http://koan.studentenweb.org/software/jpeg2pdf.html
Ruby Application Archive page:
http://raa.ruby-lang.org/project/jpeg2pdf/

This is a beta release. Feel free to comment.

Regards,

Koen Vervloesem

 

[Austin Ziegler]

Hi,

I'm pleased to announce you jpeg2pdf version 0.1.

jpeg2pdf is a free program that converts a directory of JPEG files to a
PDF file.

Koen,

It will be some time before I can attack this problem again, but would
it be acceptable for me to integrate this code into PDF::Writer, as
that is a weakness of PDF::Writer?

-austin

 

[gabriele renzi]

Koen Vervloesem ha scritto:

Hi,

I'm pleased to announce you jpeg2pdf version 0.1.

thank you!
I can think of at least one time when I'd have love to have this:
convertin a magicpoint presentation (about ruby, of course into pdf.
And as Austin Ziegler already pointed out at that time PDF::Writer was
someway broken in relation to this.
I'll try it and report any problem (wishing I have nothing to report

 

[Joao Pedrosa]

Hi,

It will be some time before I can attack this problem again, but would
it be acceptable for me to integrate this code into PDF::Writer, as
that is a weakness of PDF::Writer?

I've just uploaded my copy of PDF::Writer to a public site:
http://www.geocities.com/joaopedrosa//pdfw.html

It contains some modifications, though they aren't commented.

If you can run a diff, at least they will point out where it needs some fixes.

With your lib, I've done this:
http://geocities.com/joaopedrosa/reporting.html

But those samples were made to show up my lib to a friend, and the
texts are in Portuguese. So disregard them and just check out the
results (images or pdfs) and the code below.

I hope to some day release my pdf lib too, which is based on yours, of course.

Thanks for it!

Cheers,
Joao

 

[Koen Vervloesem]

It will be some time before I can attack this problem again, but would

it be acceptable for me to integrate this code into PDF::Writer, as
that is a weakness of PDF::Writer?

You are free to integrate my code in your own under the conditions of
the X11 license.

By the way, I'm glad you're interested. I have studied PDF::Writer, but
I didn't use it because it looked a little bit overkill for my
application. A second reason is I wanted to learn the PDF specification
for myself...

Just out of curiosity: what problems do you have in PDF::Writer?

Regards,

Koen Vervloesem

 

[Fredrik Jagenheim]

Just out of curiosity: what problems do you have in PDF::Writer?

A couple of weeks ago I used PDF::Writer to autogenerate a
job-internal CV for me from a YAML file.

The two problems I found was:
* Image support didn't work
* Unable to use external fonts

Both was very simple to fix. I uploaded both patches to RubyForge, but
nothing has happened with them. The font-patch needs a few fixes
(forgot to remove a couple of debug statements) but I haven't fixed
them myself, since patches just seem to rot in RubyForge anyway.

//F

 

[Fredrik Jagenheim]

The font-patch needs a few fixes
(forgot to remove a couple of debug statements) but I haven't fixed
them myself, since patches just seem to rot in RubyForge anyway.

Hmmm... That came through way too harsh.

That wasn't my intention...

Sorry for any confusion.

//F

 

[Austin Ziegler]

A couple of weeks ago I used PDF::Writer to autogenerate a
job-internal CV for me from a YAML file.

The two problems I found was:
* Image support didn't work
* Unable to use external fonts

Both was very simple to fix. I uploaded both patches to RubyForge, but
nothing has happened with them. The font-patch needs a few fixes
(forgot to remove a couple of debug statements) but I haven't fixed
them myself, since patches just seem to rot in RubyForge anyway.

Fair enough; in my defence, though, my priority lately has been Ruwiki
-- and during RubyConf, my main development computer crashed.

Your patches will be merged in CVS-latest (manually, so that I can
make sure the debug statements are gone . It will be some time
before I can make a new release that contains these, because I have
several other things that need attention as well.

There is a gemspec available for PDF::Writer as well, so when I *do*
release the new version, it will be available as a Gem.

-austin

 

[Fredrik Jagenheim]

Fair enough; in my defence, though, my priority lately has been Ruwiki
-- and during RubyConf, my main development computer crashed.

Yes, I realize that I said it like some needy child and I apologize for that.

Your patches will be merged in CVS-latest (manually, so that I can
make sure the debug statements are gone . It will be some time
before I can make a new release that contains these, because I have
several other things that need attention as well.

It's no hurry for me, I already have the patches in my version.

Also, the patches should be fairly straightforward. Most of the code
to support both images and fonts where already there. Just a couple of
bugs / missing parts that hindered them from working properly.

Actually, I think you should hurry and get a new release out and NOT
call it a 'technology preview'. I spent many days trying to figure out
how to generate PDF files in Ruby looking at interfaces to commercial
libs that left waterstamps on the pages, interfaces to libs that
refused to compile and interfaces that hadn't been updated since Ruby
0.1. Yours was the last I looked at just because you announced it as
'broken from start', instead it contained support for /everything/ I
needed and worked just perfectly.

BR,
//F