All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Sweet <mike@easysw.com>
To: TORATANI Yasumasa <toratani.yasumasa@canon.co.jp>
Cc: Till Kamppeter <till.kamppeter@gmx.net>,
	printing-architecture <printing-architecture@freestandards.org>,
	"desktop_printing@osdl.org" <desktop_printing@osdl.org>
Subject: Re: [Printing-architecture] Re: [Desktop_printing] Re: Trying out sample implementation of japanese OpenPrinting efforts
Date: Tue, 16 May 2006 06:54:38 -0400	[thread overview]
Message-ID: <4469AF6E.40707@easysw.com> (raw)
In-Reply-To: <20060516114211.A670.TORATANI.YASUMASA@canon.co.jp>

TORATANI Yasumasa wrote:
> Hi,
> 
> I think the common statement that we will shift to PDF as a new printing
> spooling format is reasonable.
> 
> On the other hand, when a CUPS filter handles the PDF data, I think the
> filter needs to access the entire PDF file, so, in case of long page document,
> for instance over 100 pages document, does pdftopdf convert 100 pages PDF
> into layouted 100 pages PDF, and save it into disk, and after completion of
> saving 100 pages PDF data, pdfto* filter starts to read the saved PDF data
> from the disk, and converts it into raster, PDL, etc?  Or, does pdftopdf send
> some header including some PDF table info. to pdf* filter via stdin/stdout,
> before sending the PDF document body data?

Those are implementation details - we're a bit too early in the
process set those in stone.  In general, we *will* need to save the
printer-specific PDF file (application/vnd.cups-pdf, already
registered with IANA) to disk in the pdftops/pdftoraster filter,
however the document filter (pdftopdf) can probably stream the
objects through the use of indirect objects to hold the stream
lengths.

That said, an alternative solution would be to put the job filtering
in pdftops/pdftoraster themselves, in which case pdftopdf will only
be necessary when printing to a PDF-capable printer.  The current
Xpdf/poppler APIs are insufficient for this right now, but if
implemented properly it would provide a highly efficient filtering
solution.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com


  reply	other threads:[~2006-05-16 10:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44664EAA.2030508@gmx.net>
     [not found] ` <20060515113357.A61C.TORATANI.YASUMASA@canon.co.jp>
2006-05-15 11:19   ` [Printing-architecture] Re: [Desktop_printing] Trying out sample implementation of japanese OpenPrinting efforts TORATANI Yasumasa
     [not found] ` <4468D32D.40005@gmx.net>
2006-05-15 19:41   ` [Printing-architecture] Re: [Desktop_printing] " Michael Sweet
     [not found]     ` <4468EF42.8060502@gmx.net>
2006-05-16  3:22       ` TORATANI Yasumasa
2006-05-16 10:54         ` Michael Sweet [this message]
     [not found] ` <4467B9FD.6030005@gmx.net>
     [not found]   ` <20060515183801.A638.TORATANI.YASUMASA@canon.co.jp>
     [not found]     ` <4468CAFA.9030408@gmx.net>
     [not found]       ` <4468E039.5000304@gmx.net>
2006-05-15 20:45         ` [Printing-architecture] Re: [Desktop_printing] Deprecate IJS? GhostScript with only "opvp" as output device? Michael Sweet
     [not found]           ` <4468ECB9.5060507@gmx.net>
2006-05-16  0:16             ` Michael Sweet
     [not found]     ` <4468BEE7.80501@gmx.net>
2006-05-16  5:26       ` [Printing-architecture] Re: [Desktop_printing] Re: Trying out sample implementation of japanese OpenPrinting efforts TORATANI Yasumasa
     [not found]         ` <4469922E.9060301@gmx.net>
2006-05-16  8:56           ` TORATANI Yasumasa

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=4469AF6E.40707@easysw.com \
    --to=mike@easysw.com \
    --cc=desktop_printing@osdl.org \
    --cc=printing-architecture@freestandards.org \
    --cc=till.kamppeter@gmx.net \
    --cc=toratani.yasumasa@canon.co.jp \
    /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.