-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
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:
ColorModeis used instead ofColorModel, which prevents mapping of the color space by CUPS- The value name is
Monochromeinstead ofGray(orBlack), which is not a known-good name according to CUPSscheduler/colorman.c - The value name is
Colorfor color, which is also not valid (CUPS expectsRGBorCMYKorDeviceN)
foo2zjs/foomatic-db/opt/foo2hbpl2-ColorMode.xml
Lines 21 to 27 in 43b8bfa
| <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:
- Patch foo2zjs foomatic DB to use
ColorModeland addGray/RGB, regenerate all PPD files - Patch cups-filters
cups-filters/filter/foomatic-ripto mapColorModeltoColorMode(will CUPS behave withoutColorModel Gray/RGBin 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