4 people 505c4a2fa3 Issue #248: pdfcraft-cli render writes the format its --out name says (.png, .jpg, .tif or .pam) (#255) ...

`render --out p1.png` wrote a netpbm PAM stream (P7) whatever the name,
so a `.png` could not be opened by any PNG reader. The CLI already links
the engine, whose export module encodes PNG, JPEG and TIFF, so the output
format now follows the extension: `.png`, `.jpg`/`.jpeg` (quality 90),
`.tif`/`.tiff`, and `.pam` for the raw stream as before. Any other name
is refused up front, before the page is rendered, with the accepted list.

`export::encode_image` wraps the three encoders behind `ImageFormat` so
the CLI and `Exporter::image` share one match.

Tests (apps/pdfcraft-cli/tests/render.rs): a `.png` gets the PNG
signature and an IHDR with the rendered size; `.JPG` and `.tif` get
JPEG/TIFF magic; `.pam` still gets the P7 header and the right number of
bytes; `.bmp` fails with the message and writes nothing.

Co-authored-by: wstock <[email protected]>
Co-authored-by: Claude Fable 5.1 <[email protected]>
Co-authored-by: Brandon Thomas <[email protected]>

2026-10-08 07:25:43 -04:00

..

edit.rs

CLI: edit rejects unknown options instead of writing an unchanged copy (#133) (#227)

2026-10-08 03:39:27 -04:00

render.rs

Issue #248: pdfcraft-cli render writes the format its --out name says (.png, .jpg, .tif or .pam) (#255)

2026-10-08 07:25:43 -04:00

run_root.rs

Security: --root confinement leaks and escapes (#136, #137) (#164)

2026-10-07 21:12:32 -04:00

stdout.rs

Restore #196, #202, #203 and the macOS release-runner change, reverted by the i18n chain (#229)

2026-10-08 03:33:35 -04:00

text.rs

CLI: text fails when the document cannot be opened (#132) (#233)

2026-10-08 04:25:52 -04:00