All of lore.kernel.org
 help / color / mirror / Atom feed
From: Per Hermansson <hermansson.per@bredband.net>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Common Printing Dialog: Print to (PDF) file
Date: Thu, 08 Oct 2009 19:06:02 +0200	[thread overview]
Message-ID: <4ACE1BFA.80106@bredband.net> (raw)
In-Reply-To: <4A8BCB46.9070401@gmail.com>

Till Kamppeter wrote:
> Hi,
>
> the final design planning is that all applications should have "Export 
> to PDF ..." in their file menus (like OpenOffice.org) with a dedicated 
> dialog, similar to the CPD but yet to be designed by OpenUsability.
>
> As this will take time and the current Qt and GTK printing dialogs 
> contain a "Print to File" facility which appears as an extra print 
> queue, we should implement such a "Print to File" queue also in the 
> Common Printing dialog, so that we get it quickly into the distros 
> without having a regression due to this feature missing.
>
> For the implementation note that the current dialogs do not send the 
> job into a CUPS queue for "Print to File" (we do not use facilities 
> like the cups-pdf package). "Print to File" opens a "Save as ..." 
> dialog when clicking on "Print" in the printing dialog. Then the user 
> chooses where to put his file. This process is completely done by the 
> printing dialog running as the calling user, nothing done by CUPS for 
> it. At least GTK allows to choose between PostScript and PDF for such 
> a file. For your implementation PDF would be the most important, 
> PostScript can perhaps be dropped if it makes it too complicated.
This part has been implemented in the GTK version of the CPD and is 
available in the bazaar repo.
Better late then never :-)
> It would be great if you could implement that in the Common Printing 
> Dialog, ideally with a possibility for the application to suppress 
> this feature (Lars, perhaps this needs an additional boolean parameter 
> in the CPDAPI).
>
No such checks are made yet but it should be easy to fix if we decide to 
update the CPDAPI.

/Per

  reply	other threads:[~2009-10-08 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  9:52 [Printing-architecture] Common Printing Dialog: Print to (PDF) file Till Kamppeter
2009-10-08 17:06 ` Per Hermansson [this message]
2009-10-08 17:41 ` Hal V. Engel
2009-10-08 20:06   ` Per Hermansson

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=4ACE1BFA.80106@bredband.net \
    --to=hermansson.per@bredband.net \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@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.