All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: "printing-foomatic@lists.linux-foundation.org"
	<printing-foomatic@lists.linux-foundation.org>,
	Open Printing <printing-architecture@lists.linux-foundation.org>,
	Printing-japan <printing-japan@lists.linux-foundation.org>,
	Didier 'OdyX' Raboud <didier@raboud.com>,
	Warll Dressler <warll.dressler@gmail.com>,
	Lars Uebernickel <larsuebernickel@gmx.de>
Subject: [Printing-architecture] ANNOUNCE: Foomatic 4.0.6 released!
Date: Wed, 15 Dec 2010 18:20:25 +0100	[thread overview]
Message-ID: <4D08F8D9.3070403@gmail.com> (raw)

Foomatic 4.0.6 is released and now available for download [1].

This release fixes several bugs which got reported to us in the past 4 
months.

foomatic-rip does not only have several potential crashes fixed but now 
also the automatic input data format recognition (PDF or PostScript) 
works when the input data is preceded by PJL and for non-CUPS use the 
text filter setting of the config file is only used if the selected text 
filter is actually supported.

In foomatic-db-engine the foomatic-ppd-to-xml script to generate printer 
XML entries from PPDs is much more flexible now. It allows personal 
comments for the XML entry, suppressing automatic adding of drivers 
based on supported page description languages, and generating an XML 
entry also for more than one PPD file (for the same printer).

All XML files generated by foomatic-db-engine now have the same 
formatting (spaces, indentations, order of drivers in driver list) as it 
is used by the OpenPrinting web server. This way unnecessary automatic 
commits to the BZR repository with only white space changes are avoided.

The DB.pm Perl module handles failures of the C helper programs 
gracefully now.

The PPD file generator foomatic-ppdfile (or 
/usr/lib/cups/driver/foomatic) now handles driver names with dashes 
(like "hpijs-pcl5e") correctly.

Already for a longer time it was possible to use some special entities 
in the code pieces to build the renderer command line. These entities 
get replaced by job parameters, like the job ID, the user who sent the 
job, the job title, date, number of copies, ... when a job is rendered 
by foomatic-rip. This release now adds documentation for this feature in 
the README file of foomatic-db-engine and it improves the feature by 
adding the possibility to limit the length of the strings to be inserted 
for the entities. This is very helpful for printers which use such 
parameters but abort the job or even crash if the strings are too long.

Thanks to everyone who reported bugs to us (or to their distributions) 
or sent feature requests.

Have a lot of fun with the new Foomatic release!

    Till


[1]https://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/foomatic


                 reply	other threads:[~2010-12-15 17:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D08F8D9.3070403@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=didier@raboud.com \
    --cc=larsuebernickel@gmx.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=printing-foomatic@lists.linux-foundation.org \
    --cc=printing-japan@lists.linux-foundation.org \
    --cc=warll.dressler@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.