Re: [Printing-architecture] [Printing-summit] Issue list from HP

[Till Kamppeter <till.kamppeter@gmail.com>]

Robert Krawitz wrote:
>    Date: Wed, 15 Apr 2009 13:47:39 +0200
>    From: Till Kamppeter <till.kamppeter@gmail.com>
> 
>    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
> 
> Like this?
> 
> *PageSize Letter.Full/Letter:	"<</PageSize[612 792]/cupsPageSizeName (Letter.Full)/ImagingBBox null>>setpagedevice"
>

Yes, exactly this way.

If a PDF workflow is used or an image is directly sent to CUPS there is 
no PostScript data stream involved. In these cases the pdftoraster and 
imagetoraster filters parse the PostScript code in the PPD file via a 
CUPS library function and so alo in this case both the paper size in 
numbers and the paper size name get made use of.

>    > PCFileName is a *real* crock these days.
> 
>    Is it really needed in real life?
> 
> Seems to me that everything newer than Windows 3.1 supports long file
> names.  We just generate names like STP00001.PPD, which aren't stable
> from release to release (when we add new printers).
> 

Here we only need to satisfy the specs somehow. This is one method.

    Till