From: Till Kamppeter <till.kamppeter@gmail.com>
To: Robert Krawitz <rlk@alum.mit.edu>
Cc: printing-architecture@lists.linux-foundation.org,
printing-summit@lists.linux-foundation.org,
martin.pitt@ubuntu.com, Michael R Sweet <msweet@apple.com>
Subject: Re: [Printing-architecture] [Printing-summit] Issue list from HP
Date: Wed, 15 Apr 2009 13:47:39 +0200 [thread overview]
Message-ID: <49E5C95B.4080304@gmail.com> (raw)
In-Reply-To: <200904151139.n3FBdmZJ030596@dsl092-065-009.bos1.dsl.speakeasy.net>
Robert Krawitz wrote:
> Date: Tue, 14 Apr 2009 21:03:24 -0700
> From: Michael R Sweet <msweet@apple.com>
>
> Robert Krawitz wrote:
> > ...
> > There is a CUPS API call named ppdPageSize that should get the
> > *actual* named paper size. We had this kind of issue with Gutenprint
> > a while back; that turned out to be the solution.
>
> There is also a cupsPageSizeName attribute that can be set by
> drivers that need to know which version of a size was selected.
>
> Is that just
>
> *cupsPageSizeName: True
>
> in the top section of the file?
>
No, there is a special PostScript expression:
<</cupsPageSizeName (A4.Full)>>setpagedevice
So the PostScript code of each paper size must be
<</PageSize[595 842] /cupsPageSizeName (A4.Full)>>setpagedevice
pdftoraster supports this, too.
> > I think we've had one or two cases of something that was accepted in
> > an older version of CUPS (and not getting flagged by cupstestppd)
> > being rejected by a newer version. It was either resolution names or
> > option names or values greater than 40 bytes or so.
>
> Resolution names and the PCFileName stuff come to mind. There have
> been issues with the lengths of translation strings, too.
>
> PCFileName is a *real* crock these days.
>
Is it really needed in real life?
Till
next prev parent reply other threads:[~2009-04-15 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46089FAF7804194C8AD6458E272B07182174584144@GVW0676EXC.americas.hpqcorp.net>
2009-04-14 23:22 ` [Printing-architecture] Issue list from HP Till Kamppeter
[not found] ` <200904150120.n3F1Kg95023375@dsl092-065-009.bos1.dsl.speakeasy.net>
[not found] ` <49E55C8C.2010500@apple.com>
[not found] ` <200904151139.n3FBdmZJ030596@dsl092-065-009.bos1.dsl.speakeasy.net>
2009-04-15 11:47 ` Till Kamppeter [this message]
[not found] ` <200904151206.n3FC6n7j030700@dsl092-065-009.bos1.dsl.speakeasy.net>
2009-04-15 14:28 ` [Printing-architecture] [Printing-summit] " Till Kamppeter
[not found] ` <alpine.LNX.2.00.0904151216120.10560@nelson.suse.de>
[not found] ` <49E5D2AB.7000000@redhat.com>
2009-04-15 14:41 ` [Printing-architecture] " Till Kamppeter
2009-04-27 16:16 ` 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=49E5C95B.4080304@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=martin.pitt@ubuntu.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-summit@lists.linux-foundation.org \
--cc=rlk@alum.mit.edu \
/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.