Skip to content

No standard color/grayscale mapping due to ColorMode instead of ColorModel #1

@ValdikSS

Description

@ValdikSS

Foomatic database of foo2zjs driver set uses ColorMode option to choose color or grayscale (monochrome) printing, but the standard option is ColorModeL.
This prevents selecting color/grayscale printing using standard CUPS printing options, and also makes it impossible to choose over IPP.

Issues:

  1. ColorMode is used instead of ColorModel, which prevents mapping of the color space by CUPS
  2. The value name is Monochrome instead of Gray (or Black), which is not a known-good name according to CUPS scheduler/colorman.c
  3. The value name is Color for color, which is also not valid (CUPS expects RGB or CMYK or DeviceN)

<enum_val id="ev/foo2hbpl2-ColorMode-mono">
<ev_longname> <en>Monochrome</en> </ev_longname>
<comments><en>
Prints in monochrome only
</en></comments>
<ev_shortname> <en>Monochrome</en> </ev_shortname>
<ev_driverval></ev_driverval>

Possible solutions:

  1. Patch foo2zjs foomatic DB to use ColorModel and add Gray/RGB, regenerate all PPD files
  2. Patch cups-filters cups-filters/filter/foomatic-rip to map ColorModel to ColorMode (will CUPS behave without ColorModel Gray/RGB in the PPD though?)

I don't know the reason behind using this exact option name. It was probably done on purpose.

@tillkamppeter thoughts?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions