Re: How to create a PDF-Printer from the command line
On Wed 10 Jan 2018 at 21:01:13 +0100, firstname.lastname@example.org wrote:
> On Wed, Jan 10, 2018 at 07:10:03PM +0000, Brian wrote:
> > On Wed 10 Jan 2018 at 17:13:09 +0100, email@example.com wrote:
> > > Downside is that it does the panoramic tour via PS and thus generates
> > > fairly hefty PDFs.
> > With plain text files as an input?
> > brian@desktop3:~$ ls -l
> > -rw-r--r-- 1 brian brian 28853 Jan 10 18:58 output1.pdf
> > -rw-r--r-- 1 brian brian 66557 Jan 10 18:58 output1.ps
> > -rw-r--r-- 1 brian brian 36221 Jan 10 18:58 output2.pdf
> > -rw-r--r-- 1 brian brian 219186 Jan 10 18:59 output3.pdf
> > output3.pdf contains the complete DejaVuSansMono glyph set.
> > The finger is often pointed at ps2pdf as a file bloating command.
> > Unjustifiably, it would seem, in this case. A counter example with a
> > text file?
> Thanks for actually trying out. I stand corrected...
A gracious response. However, my data were in the context of using a2ps
to go from text to PS. Your "hefty PDFs" would be entirely correct if
paps had been used for the conversion. The result is a 156551 sized file
for me. gs2pdf comes up with a whopping 11540827 and takes 18 s to do so.
An explantation is given by a Ghostscript developer at
The same page has
> As the author of paps,...I have just released a new version of paps...
The new version's README has
> paps is a command line program for converting Unicode text
> encoded in UTF-8 to postscript and pdf by using pango.
That was in 2015, Debian's paps does not relect the existence of a
7.0 version. I wonder why?