From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49E5C95B.4080304@gmail.com> Date: Wed, 15 Apr 2009 13:47:39 +0200 From: Till Kamppeter MIME-Version: 1.0 References: <46089FAF7804194C8AD6458E272B07182174584144@GVW0676EXC.americas.hpqcorp.net> <49E51AB7.2010902@gmail.com> <200904150120.n3F1Kg95023375@dsl092-065-009.bos1.dsl.speakeasy.net> <49E55C8C.2010500@apple.com> <200904151139.n3FBdmZJ030596@dsl092-065-009.bos1.dsl.speakeasy.net> In-Reply-To: <200904151139.n3FBdmZJ030596@dsl092-065-009.bos1.dsl.speakeasy.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] [Printing-summit] Issue list from HP List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Robert Krawitz Cc: printing-architecture@lists.linux-foundation.org, printing-summit@lists.linux-foundation.org, martin.pitt@ubuntu.com, Michael R Sweet Robert Krawitz wrote: > Date: Tue, 14 Apr 2009 21:03:24 -0700 > From: Michael R Sweet > > 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: <>setpagedevice So the PostScript code of each paper size must be <>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