mirror of
https://github.com/storytold/craft-libs.git
synced 2026-10-31 23:59:16 +00:00
magdale76andClaude Opus 5.5
bfbf82b360
The Windows job ticket always named a colour: Monochrome when the job asked for grayscale, Color otherwise. Merged over the user's printing preferences, that Color replaced a black and white the user had picked in the driver's own Properties dialog, so the job came out in colour (storytold/pdfcraft#2422). The ticket now names a colour only when grayscale is asked for. Without it the driver validates the ticket from the user's preferences, as the CUPS backend and `verify_job_options` already assumed. Checked on an HP OfficeJet 250 (PCL-3 driver) with its preferences set to black and white: the validated ticket had psk:Color and the DEVMODE dmColor 2 before, psk:Monochrome and dmColor 1 after. With colour preferences it is psk:Color either way. - `the_ticket_carries_the_job_options`: no PageOutputColor without grayscale (fails on the old ticket). - `the_preferences_colour_reaches_a_job_without_grayscale` (ignored, needs CRAFT_PRINT_TEST_PRINTER; sends no job): the job's validated colour equals the preferences' colour. Fails on the old ticket with the queue set to black and white; passes on HP OfficeJet 250, Microsoft Print to PDF and OneNote. - The Windows command preview says `color=(driver default)`, like `duplex=(queue default)`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>