mirror of
https://github.com/storytold/pdfcraft.git
synced 2026-10-28 20:18:06 -06:00
37076662a7
* D5: README for cos and engine, and an honest cos status line Thirteen crates have no README, although the session protocol tells every session to read the README of the crate it is touching. These are the two biggest: cos is where every hostile file lands first, and engine is the whole API surface a frontend gets. Each states its layer and the rules that bind it, sketches the API against the real signatures, and ends with what is deliberately not done. The cos README spells out the clone-is-a-snapshot property and why both writers return bytes rather than taking a sink; the engine README spells out the four-step editing model that makes what you see what Save writes. Also corrects the module doc on cos/src/lib.rs, which still said encryption and object-stream output for full saves were not done. Both shipped: security.rs handles R2-R6 with crypt filters and /EFF, and SaveOptions::object_streams defaults to true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * Preserve alternate appearances and indirect push-button values Keep rollover, down and custom appearance entries when normal appearances are regenerated, without modifying shared dictionaries. Resolve indirect button caption and layout values. Cover full and incremental saved output, and wait for raster readiness in the existing Linux scroll test. Co-authored-by: Codex <codex@openai.com> * M7: select and edit grouped Form XObject figures Co-Authored-By: Codex <noreply@openai.com> * M14: let neutral Windows locales fall through to display language Co-authored-by: Codex <codex@openai.com> * pdfcraft-cli --help lists `mcp` only when the build has it Follow-up to #540: a build without the `mcp` feature (`--no-default-features`) still listed `pdfcraft-cli mcp` in its usage, and `pdfcraft-cli mcp` then said "unknown command". USAGE is now put together with `concat!`, and its `mcp` lines come from a macro that is empty without the feature. In such a build `pdfcraft-cli mcp` says the MCP server was left out instead of calling it an unknown command. - tests/help.rs: usage_lists_mcp_only_when_built_with_it (runs in both feature sets) and mcp_without_the_feature_says_it_was_left_out (without the feature) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * engine README: the execution plan is local-only, so don't link a path that doesn't exist --------- Co-authored-by: Tanish Manku <tmanku.dev@gmail.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: sanyamsingh001 <314051937+sanyamsingh001@users.noreply.github.com> Co-authored-by: Codex <codex@openai.com> Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Streetblock <github@streetblock.de> Co-authored-by: lloyd <lloyd@stackworx.io> Co-authored-by: Brandon Thomas <echelon@gmail.com>
24 lines
1.5 KiB
Markdown
24 lines
1.5 KiB
Markdown
# Editing existing images and figures
|
|
|
|
In **Edit a PDF → Edit text and images**, click a figure to select it. Drag the selected
|
|
figure to move it, drag a corner to resize it proportionally, or press Delete to remove
|
|
that placement. The context menu also rotates or flips it. Changes support undo and
|
|
survive saving/reopening.
|
|
|
|
PDF figures are not always bitmap images. Imported diagrams often use a **Form XObject**,
|
|
which packages text, vector paths, and nested images into one object. PdfCraft selects
|
|
this object using its `BBox` and optional `Matrix` and edits it as a whole. Its original
|
|
content, resources, clipping box, and transparency settings remain intact. Moving or
|
|
deleting one use of a shared figure does not alter its other placements or pages.
|
|
|
|
**Replace Image** and **Save Image As** apply only to raster Image XObjects; these menu
|
|
items are disabled for grouped Form artwork. The tool does not ungroup Forms, edit their
|
|
individual internal elements, select arbitrary ungrouped vector paths, or edit inline
|
|
images (`BI`/`ID`/`EI`). A Form's bounding box may include whitespace.
|
|
|
|
For automation, `page_images` lists both kinds with `kind: "image"` or `kind: "form"`.
|
|
Forms have `pixels: [0, 0]`, since they have no single bitmap resolution. Use the returned
|
|
number with `image_edit` (move, rotate, flip_horizontal, flip_vertical, delete).
|
|
Coordinates are top-left-origin page points. `image_save` and `image_edit`'s replace action
|
|
return a clear error for Form artwork.
|