Re: Citizen CX-02 incorrect paper dimensions in PPD

ValdikSS via Gimp-print-devel <[email protected]> Wed, 31 Jul 2024 18:13:11 +0300
Newsgroups	gmane.linux.printing.gimp-print.devel
Message-ID	<[email protected]>
On 31.07.2024 17:42, Solomon Peachy wrote:
> I'm having a very hard time following what you pasted here, so I'll
> extract the definitions for one size from the PPD:
> 
> *PageSize B7/3.5x5:     "<</PageSize[261.120 460.800]/ImagingBBox null>>setpagedevice"
> *ImageableArea B7/3.5x5:        "0.000 44.640 261.120 416.160"
> *PaperDimension B7/3.5x5:       "261.120 460.800"
> 
> PageSize and PaperDimension are identical, and ImageableArea is smaller
> because of how the printer works.
> 
> ....This appears to be perfectly fine and is completely compliant with
> PPD-based printing flows, which one would expect for something designed
> around PPDs.

Hi Solomon,
I'd expect 3.5x5 PageSize to contain "252 360" value instead of "261.120 
460.800".
If I modify .ppd file with the values calculated by multiplying inches 
by 72, CUPS starts to report these values as an IPP-defined media sizes.

Michael Sweet, the developer of CUPS, told to report this as a bug to you:
https://github.com/OpenPrinting/cups/issues/1017#issuecomment-2259205981

Also I'm not sure why there are same PageSize values used for different 
page sizes, for example:

*PageSize w243h432/3.375x6:	"<</PageSize[297.600 460.800]/ImagingBBox 
null>>setpagedevice"
*PageSize w270h432/3.75x6:	"<</PageSize[297.600 460.800]/ImagingBBox 
null>>setpagedevice"
*PageSize w288h432/4x6:	"<</PageSize[297.600 460.800]/ImagingBBox 
null>>setpagedevice"


> The CX-02 is a full-bleed printer; in order to guarantee edge-to-edge
> printing the image data has to extend past the physical edges of the
> paper. So if we lie about the supported resolution (eg 1800x1200 for a
> perfect 10x15cm at 300dpi) then if we don't lossily re-scale the image
> to fit the printer's native resolution, we are all but guaranteed to end
> up with visible white margins on at least one edge of the print.

I see. Should PageSize/PaperDimension use extended values in this case? 
Isn't that controlled by ImageableArea?


> ...Meanwhile, you didn't say what version of cups, cups-filters, or
> gutenprint is in use, nor what IPP client is exhibiting this
> misbehavior.

Check the link above: instead of reporting e.g. na_index-4x6_4x6in, CUPS 
reporting custom_117.35x162.56mm_117.35x162.56mm

The printer is shared by CUPS 2.4.2, cups-filters 1.28.17, gutenprint 
5.3.4.20220624T01008808d602. This is Debian 12 system.

The clients are Windows 10/11, Android 10 (check the link for more info).

If this this seem like a bug in CUPS to you, please report details here 
or to the ticket above. I'm not at all skilled in PostScript and .ppd files.

_______________________________________________
Gimp-print-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
OpenPGP_signature.asc (application/pgp-signature, 840 B)