3 people 1952a88801 fix(cli): use laid-out pages for dynamic XFA forms (#2813) ...

Fixes #1645. For a dynamic XFA form, `info` reported the placeholder
page and field counts, and `text` and `render` read the placeholder
pages, while the app and the automation tools lay the template out.

The CLI now opens dynamic XFA forms through the engine session and uses
its laid-out document for page and field metadata, text and pixels.
`info` keeps the input's file size and also reports the original counts
as `pdf_pages` and `acroform_fields`; `text` checks the copy permission
before extracting. The input file is never written.

Checks run (rustc 1.99.0): cargo fmt --check; cargo clippy -p
pdfcraft-cli --all-targets -- -D warnings; cargo test -p pdfcraft-cli;
cargo xtask layers; cargo xtask assets.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Brandon Thomas <echelon@gmail.com>

2026-10-18 09:54:00 -04:00

..

src

fix(cli): use laid-out pages for dynamic XFA forms (#2813)

2026-10-18 09:54:00 -04:00

tests

fix(cli): use laid-out pages for dynamic XFA forms (#2813)

2026-10-18 09:54:00 -04:00

build.rs

CLI: pdfcraft-cli.exe carries a Windows version resource (#598)

2026-10-09 19:09:23 -04:00

Cargo.toml

M1: every PDF leaves the engine checked, and every writer uses one staging-file writer (#2166) (#2182)

2026-10-15 02:48:09 -04:00