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>
Craft App Libraries
This repo contains libraries used by the various Craft Apps. It's a Rust monorepo workspace, and the libraries can be included by any Craft Apps that need them.
In the future this may grow to include non-Rust library code.
If any libraries grow beyond Craft App usage, eg. RAW format support, they may be promoted out and into their own libraries for the broader ecosystem to take advantage of.
Layout
A Cargo workspace (edition 2024, resolver 3). Each library is a crate under crates/<name>, named
craft-<name>, with version, edition, license and repository inherited from the workspace
(license.workspace = true, and so on) and [lints] workspace = true. Register each crate in
[workspace.dependencies] in the root Cargo.toml.
Apps depend on a crate by git:
craft-<name> = { git = "https://github.com/storytold/craft-libs", rev = "<commit>" }
Libraries
-
craft-pdf: independently optional PDF parsing, interpretation, rasterization and guarded authoring. Apps retain layout, fonts, editing and export policy; writer-only consumers do not enable the shared reader. -
craft-atomic: Crash-safe atomic file writing and replacement with same-directory staging, directory fsync, AppleF_FULLFSYNCfallback, transient lock backoff, and fault injection for the Craft suite. -
craft-cms: pure-Rust ICC v2/v4 colour management: profile parsing and writing, transforms, rendering intents, black point compensation, soft proofing, gamut checks, 3D LUTs and built-in profiles (sRGB, Display P3, synthetic coated CMYK and others). -
craft-print: PDF submission to CUPS and Windows, printer discovery, duplex/copies/colour and driver preferences. PDF generation stays in each app. -
craft-quit: native macOS quit, egui close handling and an optional app menu. Unsaved-document decisions and save prompts stay in each app. -
craft-settings:config.tomlsettings storage for every app: platform folders, portable mode and overrides, atomic saves while running, backup, damaged-file recovery and schema migrations. Policy in docs/settings-storage.md. -
craft-ui: SVG catalogs, icon buttons, tabs, pane controls, transactional docking, print settings and theme helpers for egui frontends; assets, themes, localization and command handling stay in each app. Requires Rust 1.95 or later. -
Shared UI component audit: source inventory, extraction priorities and compatibility boundaries across the Craft suite.
-
Theme infrastructure: eight-app comparison and the small shared widget-state styling boundary.
-
Panel docking: validated panel moves, floating groups, workspace adapters and an optional egui docking surface.
License and credits
craft-libs is dual-licensed under MIT or Apache-2.0, at your option. Copyright (c) 2026 ArtCraft Team and the craft-libs contributors. Required notices are in NOTICE.
Bundled fonts, icons, images and other assets keep their own open licenses; each one is listed with its author, source and license in ATTRIBUTION.md.