Skip to content

spec(document-renderer): HTML-to-PDF engine choice and paged-media support - #579

Merged
transitrix merged 3 commits into
mainfrom
methodology/537-html-pdf-engine
Sep 2, 2026
Merged

transitrix merged 3 commits into
mainfrom
methodology/537-html-pdf-engine

Conversation

@transitrix

@transitrix transitrix commented Sep 2, 2026 •

Copy link
Copy Markdown
Owner

Summary

Specification for HTML-to-PDF rendering engine choice and paged-media CSS support. Engine choice: PrinceXML as reference renderer, caller-supplied as standing option.

This work specifies infrastructure required for landscape pages, running footers, and figure integration.

Contents

  • PDF_RENDERING_ENGINE.md: Complete specification including:

    • Engine choice (PrinceXML reference, adopter-supplied option)
    • Paged-media CSS feature matrix (required vs. recommended)
    • Integration contract (caller, engine, and Methodology responsibilities)
    • Conformance testing approach
  • README.md update: Added reference section linking to engine spec

Design notes

  • Standing shape: Caller-supplied engine (Option 3)
  • Reference implementation: PrinceXML (Option 2)
  • Rationale: Strong paged-media CSS support; Studio as primary consumer
  • Adopters may substitute if they meet the feature matrix
  • Unsupported features must be documented, never silent

Test plan

  • Spec documents required and optional paged-media CSS features ✓
  • Feature matrix is conformance basis for adopter engines ✓
  • Integration contract clarifies responsibility split ✓

transitrix and others added 2 commits September 2, 2026 19:02
…S support

Document the HTML-to-PDF rendering engine specification for document-view PDF rendering with paged-media CSS support (named pages, landscape orientation, running footers).

Engine choice: PrinceXML as reference renderer, caller-supplied as standing option. Specification includes paged-media feature matrix and integration contract for landscape pages, running footers, and figure integration work.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Signed-off-by: transitrix <automation@transitrix.com>
@transitrix
transitrix force-pushed the methodology/537-html-pdf-engine branch from 8f96796 to 8fa9599 Compare September 2, 2026 15:02
Evaluation of HTML-to-PDF rendering engines (completed 2026-09-02) shows Vivliostyle is the optimal reference renderer choice over PrinceXML:

- Vivliostyle: Complete paged-media CSS support, actively maintained (Aug 2026), open-source (AGPL-3.0/MPL-2.0), Node.js native
- PrinceXML: Commercial (,800+/seat), licensing barrier for open-source methodology and adopters

Standing shape remains caller-supplied (Option 3); reference renderer (Option 2) is Vivliostyle. Adopters may substitute if they satisfy the paged-media feature matrix.

Signed-off-by: transitrix <automation@transitrix.com>
@transitrix
transitrix merged commit b522b05 into main Sep 2, 2026
11 checks passed
@transitrix
transitrix deleted the methodology/537-html-pdf-engine branch September 2, 2026 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant