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.

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));

Add oxml-layout = { version = "0.12.1", default-features = false } to your dependencies. Enable the default system-fonts feature only when host font discovery is intended.