graphics
in [Perl]
|
Prev: stuff
Next: FAQ 6.16 How can I do approximate matching?
From: Mart van de Wege on 10 Jun 2010 16:37 RedGrittyBrick <RedGrittyBrick(a)spamweary.invalid> writes: > On 10/06/2010 03:08, Ilya Zakharevich wrote: >> Myself, I would go through enscript or TeX - this would cover the >> typesetting needs > > I also use enscript and a2ps. I found writing TeX (or rather LaTeX) > still needs a lot of markup and the production chain can be > complicated and prone to generating mysterious error messages. What > TeX toolset do you use? > Not speaking for Ilya, but at work I had to write something to generate reports. I used SVG::TT:Graph to generate the graphs, Image::Magick to convert them to PNG, Template Toolkit to build LaTex files referring to the images, and LaTeX::Driver to render the LaTeX to PDF. Works like a charm, even if the toolchain is long. LaTeX::Driver is a bit finicky if you don't clean up your working directory though. Mart -- "We will need a longer wall when the revolution comes." --- AJS, quoting an uncertain source.
From: Ilya Zakharevich on 10 Jun 2010 23:19 On 2010-06-10, RedGrittyBrick <RedGrittyBrick(a)spamweary.invalid> wrote: >> Generating PDF might be easy (did not try it), > Yes, there appear to be some good CPAN modules for writing PDF. >> and it is much easier to print... > This isn't something I find any problems with. Most laser printers above > entry level will support PostScript printing. Some of them support PDF > printing. Most (if not all) Unix/Linux systems will have print systems > that can rasterise PostScript for non-Postscript printers. You have a wrong (IMO) metric of "having problems". PS is a programming language. There is no way to "verify" PS or debug PS: there is no way to know whether a given PS file will print on your neighbor's PS printer except for printing it. Likewise, if you can rasterize PS with one version of GS, this does not imply that it would rasterize with a different version of GS. Basically, PS leads you in the same messy can of worms as most other programming languages (only it has no debuggers or development tools). PDF, on the other hand, contains just DATA, not PROGRAM. It must be easy to verify (never tried it); then any non-buggy implementation would be able to rasterize it. >> Myself, I would go through enscript or TeX - this would cover the >> typesetting needs > > I also use enscript and a2ps. I found writing TeX (or rather LaTeX) > still needs a lot of markup and the production chain can be complicated > and prone to generating mysterious error messages. What TeX toolset do > you use? LaTeX + ams. > prefer keeping source matter in a plain text form rather than in any > proprietary form that is likely to become obsolete and unreadable. It is exactly the opposite with me. LaTeX is known to be non-backward-compatible. So I keep data in proprietary form with a known script for to-LaTeX conversion. When backward-compatibility breaks, I can compensate by editing the scripts... Yours, Ilya
From: Ted Zlatanov on 11 Jun 2010 13:19 On Thu, 10 Jun 2010 22:37:56 +0200 Mart van de Wege <mvdwege(a)mail.com> wrote: MvdW> I used SVG::TT:Graph to generate the graphs, Image::Magick to MvdW> convert them to PNG, Template Toolkit to build LaTex files MvdW> referring to the images, and LaTeX::Driver to render the LaTeX to MvdW> PDF. MvdW> Works like a charm, even if the toolchain is long. LaTeX::Driver is a MvdW> bit finicky if you don't clean up your working directory though. Any chance you can publish your toolchain to convert a series of PNG files to a PDF file? Thanks Ted
From: John Bokma on 11 Jun 2010 14:50 Ted Zlatanov <tzz(a)lifelogs.com> writes: > On Thu, 10 Jun 2010 22:37:56 +0200 Mart van de Wege <mvdwege(a)mail.com> wrote: > > MvdW> I used SVG::TT:Graph to generate the graphs, Image::Magick to > MvdW> convert them to PNG, Template Toolkit to build LaTex files > MvdW> referring to the images, and LaTeX::Driver to render the LaTeX to > MvdW> PDF. > > MvdW> Works like a charm, even if the toolchain is long. LaTeX::Driver is a > MvdW> bit finicky if you don't clean up your working directory though. > > Any chance you can publish your toolchain to convert a series of PNG > files to a PDF file? While most likely not an answer to your question, some time ago I wrote this: http://johnbokma.com/mexit/2009/02/24/jpeg-to-pdf-using-perl.html to create a pdf with one JPEG per page. -- John Bokma j3b Hacking & Hiking in Mexico - http://johnbokma.com/ http://castleamber.com/ - Perl & Python Development
From: Mart van de Wege on 11 Jun 2010 16:02
Ted Zlatanov <tzz(a)lifelogs.com> writes: > On Thu, 10 Jun 2010 22:37:56 +0200 Mart van de Wege <mvdwege(a)mail.com> wrote: > > MvdW> I used SVG::TT:Graph to generate the graphs, Image::Magick to > MvdW> convert them to PNG, Template Toolkit to build LaTex files > MvdW> referring to the images, and LaTeX::Driver to render the LaTeX to > MvdW> PDF. > > MvdW> Works like a charm, even if the toolchain is long. LaTeX::Driver is a > MvdW> bit finicky if you don't clean up your working directory though. > > Any chance you can publish your toolchain to convert a series of PNG > files to a PDF file? > Hmm. Sure thing, but it's in three fairly substantive package files. Do you want that posted here, or in a private mail? Also, I may have to anonymise our company name, which is referred to quite often in variables and directory/file names. So tell me, how do you want it? Mart -- "We will need a longer wall when the revolution comes." --- AJS, quoting an uncertain source. |