chore(deps): bump printpdf from 0.7.0 to 0.12.5

[dependabot]

Bumps printpdf from 0.7.0 to 0.12.5.

Changelog

Sourced from printpdf's changelog.

Changelog

Unreleased

Break-aware pagination is ON. HTML→PDF now goes through azul's layout_document_paged_v2 with the full BreakPolicy enabled: break-inside: avoid pushes boxes below the page break intact, widows/orphans act on paragraph line counts, line boxes are never torn mid-line across pages, table rows stay whole, and <thead> repeats on continuation pages (with its height reserved in the break calculation). Documents that never hit a break constraint paginate exactly as before; ones that do will see breaks land earlier (pushed up, bounded to a third of the page height per break). The old fixed-interval slicing is what you get from azul directly with a default BreakPolicy — printpdf no longer uses it.

The azul dependency is pinned to the git master rev that shipped the pagination and changeset refactor (aaa700097). Publishing to crates.io requires azul 0.0.14 to be published first; until then printpdf master builds from the git pin.

0.12.0

The release where OTF fonts display correctly in Acrobat again (#280), the parser grew up, the wasm demo came back from the dead, and the whole thing is verified end-to-end in a headless browser on every push.

CID-keyed CFF fonts render correctly in Acrobat and Preview (#280). Fonts like NotoSansJP carry a CID-keyed CFF whose charset does NOT map glyph ids 1:1 to CIDs (they diverge from glyph 365 on). printpdf wrote glyph ids as the Identity-H codes - but a spec-following viewer resolves every code as a CID through that charset (ISO 32000-1, 9.7.4.2), so Acrobat and Preview drew wrong CJK glyphs and nothing at all for the fullwidth brackets, while Chrome's PDFium (which falls back to code == GID) looked fine and copy-paste worked (ToUnicode was keyed by the written code). Both embed paths were wrong - the subsetter preserves the original CIDs in the subset charset while the content stream emitted renumbered sequential gids. The content stream, /W widths and /ToUnicode are now all keyed by the embedded charset's CIDs; parsing resolves codes back CID→GID (through /CIDToGIDMap streams and CFF charsets - foreign Adobe/dvipdfmx CJK PDFs re-render correctly now too, and legacy code==GID files are detected and kept stable). Guarded three ways: a deterministic mock-font suite (generated TTF/CFF/CID-CFF faces with distinct defined widths, so glyph identity is checked as arithmetic), a hard-coded-CID canary, and a fontTools CI job that re-resolves every code with Acrobat's semantics, independent of printpdf, allsorts and poppler alike. Related font-dictionary fixes: the XXXXXX+ subset tag only appears when the font was actually subset, /FontName matches /BaseFont, CIDFontType2 carries an explicit /CIDToGIDMap /Identity, .ttc sources embed the single selected face instead of the whole collection, and ToUnicode synthesis covers supplementary planes. Text-showing ops outside StartTextSection/EndTextSection - the classic "my PDF is blank" mistake (#254) - now warn loudly at save time. Type0 fonts with non-Identity-H encodings warn on parse instead of silently scrambling.

Requires rust-fontconfig 4.4.6; ships against the published `azul-layout

... (truncated)

Commits

• See full diff in compare view