All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Stephane Ascoet <Stephane.Ascoet@ac-orleans-tours.fr>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] New PDF file format in CUPS
Date: Fri, 03 Sep 2010 10:01:47 +0200	[thread overview]
Message-ID: <4C80AB6B.10202@gmail.com> (raw)
In-Reply-To: <4C809328.300@ac-orleans-tours.fr>

On 09/03/2010 08:18 AM, Stephane Ascoet wrote:
>
> Hi, I've just learned about the replacement of PS by PDF in the store file language. I wonder if this wouldn't cause unecessary
> conversions if the printer is Postscript. The application send the job in PS, CUPS store it in PDF and send it in PS to the printer?
> Why having not chosen Postscript level 3 for storage?
>

Note that the PS->PDF->PS conversion is only temporary. The applications 
are supposed to output PDF in the future. Many already do, as all KDE 
applications, some GTK applications (like evince) and from the next 
release on also OpenOffice.org.

The advantage of using PDF is mainly the smaller files, the possibility 
to reliably tell the pages apart (for printing selected pages, N-up, 
reverse order, ...), and the support for color management. PostScript, 
even level 3, does not give these advantages.

See also

https://www.linuxfoundation.org/collaborate/workgroups/openprinting/pdfasstandardprintjobformat

especially the Introduction and the section 'Related bugs and feature 
requests'.

    Till

  reply	other threads:[~2010-09-03  8:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03  6:18 [Printing-architecture] New PDF file format in CUPS Stephane Ascoet
2010-09-03  8:01 ` Till Kamppeter [this message]
2010-09-03  8:14   ` Stephane Ascoet
2010-09-03  8:24     ` Till Kamppeter

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=4C80AB6B.10202@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Stephane.Ascoet@ac-orleans-tours.fr \
    --cc=printing-architecture@lists.linux-foundation.org \
    /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.