oxml-layout

Represent fully laid-out pages in a backend-neutral form ready for PDF or raster rendering.

Capabilities

Page frames with positioned text, images, lines, rectangles, and paths.
Transforms, paints, effects, links, outlines, and logical structure.
Font discovery, shaping, metrics, and deterministic bundled fonts.
Multilingual line breaking, bidirectional text, tabs, and inline items.
Recursive groups, marked content, transforms, source ranges, and logical structure give downstream backends one complete positioned-page contract.

Measured footprint and speed

The archive row is regenerated from the complete published package that carries this README.

Measurement	Value	Version	Platform	Build mode	Input	Command	Statistic	Measured on
Crates.io archive: oxml-layout	4,900,998 compressed bytes, 9,827,172 member bytes, 60 members	0.14.2	macOS 26.6.2, Apple M5 Max, arm64	`cargo publish --workspace --dry-run --allow-dirty --locked`	Tracked `oxml-layout` package inventory	`python3 scripts/readme_doctests.py --record-measurements`	gzip archive bytes, tar member bytes, tar member count	2026-10-16

Use it when

Use this crate as the interchange layer between a format-specific layout engine and an output backend. It does not parse DOCX or PPTX and does not perform their format-specific pagination.

Relationship

rdocx-layout and rpptx-render produce this model. oxml-pdf consumes it.

Consumers that walk PageFrame::elements must recurse through PositionedElement::MarkedContent and visit its MarkedContent::children, or use oxml_layout::walk to perform recursive traversal. Because PositionedElement is non-exhaustive, a wildcard arm that ignores a new container can otherwise omit visible page content.

Example

use oxml_layout::Color;

let accent = Color::from_hex("3366CC");
assert_eq!((accent.r, accent.g, accent.b), (0.2, 0.4, 0.8));