Skip to content

v1.25.0

Latest

Choose a tag to compare

@Moonwalker1307 Moonwalker1307 released this 12 Nov 14:15
7cab532

Highlights

  • .NET 11. PdfPecker, PdfPecker.Fluent, PdfPecker.Testing and PdfPecker.Razor gain a net11.0 target next to net8.0, net9.0 and net10.0, and PdfPecker.Razor's .NET 11 build takes Microsoft.AspNetCore.Components.Web 11.0.0. The pdfpecker tool keeps installing as a Native AOT executable on a .NET 10 or 11 SDK.
  • Print-ready output: PDF/X-4 and CMYK. PdfOptions.PdfX takes the press's ICC output profile and printing condition and writes a PDF/X-4 file (ISO 15930-7) with the output intent, trim boxes inside the @page bleed, embedded fonts and sRGB tagged by profile. CSS device-cmyk() is written as DeviceCMYK for text, backgrounds, borders, rules and SVG shapes, so black text prints in black ink only.
  • PDF/A-2a and PDF/A-3a. PdfConformance.PdfA2a and PdfA3a write the accessible level: a tagged structure tree and a declared language whatever PdfOptions.Accessibility says. They combine with PDF/UA-1, and 3a carries attachments and e-invoices as 3b and 3u do. The CLI takes --pdfa 2a and --pdfa 3a.
  • Vertical Chinese and Japanese. In vertical-rl and vertical-lr, CJK characters stand upright with the font's vertical forms, as Chrome draws them (UAX #50); text-orientation (mixed, upright, sideways) and text-combine-upright: all work, and images and SVG stay upright in vertical text.
  • Khmer, Myanmar, Sinhala and Tibetan are shaped as HarfBuzz 14.6.0 does: vowel signs, subscript consonants and stacks are reordered and positioned instead of drawn in text order. All 190 texts of the HarfBuzz reference corpus match.
  • Tables across pages. Rows that start, lie under or end a rowspan now break inside at a page's end as other rows do, as in Chrome, instead of moving to the next page whole; spanning cells leave room for repeated headers, and a spanning cell's extra height is shared over its rows instead of all going to the last.
  • More CSS: ruby annotations (<ruby>, <rt>, <rp>) above their base text, text-autospace between ideographs and Latin letters or digits, font-palette and @font-palette-values for colour fonts, font-variant-alternates and @font-feature-values, and percentage heights inside flex items with a definite flexed or stretched height.
  • Closer to Chrome: solid underlines, overlines and line-throughs as thick and placed as in Chrome; translucent gradient stops interpolated premultiplied (linear-gradient(red, rgba(0,0,255,.2)) no longer turns pink at once); images keep a given height when min-width or max-width limits their width, and min-width/min-height apply to images; a flex row with an object-fit: cover image moves whole to the next page instead of leaving an empty frame.
  • PDF renderer: annotations without an appearance stream (notes, highlights, free text and other comments some tools write that way) are drawn in PDF to image and PDF to HTML, as viewers draw them, and the text of such free text is extracted with IncludeAnnotations.
  • Hostile input: overridden var(), attr() and sibling-index() declarations are skipped (a 1.24.0 regression found by the fuzzer: 6.2 s to 1.0 s), SVG filters count the pixels their content fills, the renderer charges the pixel rows that paths cross, font fallback looks at most 64 characters into a cluster, tables and positioned boxes carried through captures count against the relayout budget, and the stops added to translucent gradients are capped.

.NET 8 and 9: 1.25.0 is the last release

Microsoft ended support for .NET 8 and .NET 9 on 10 November 2026. 1.25.0 is the last PdfPecker release that targets
net8.0 and net9.0; the next release targets .NET 10 and later only. 1.25.0 and earlier releases keep working on
.NET 8 and 9. This applies to PdfPecker, PdfPecker.Fluent, PdfPecker.Testing, PdfPecker.Razor and the pdfpecker tool.

Behaviour changes

  • Ruby is laid out. <rt> annotations now sit above their base at half the font size and <rp> parentheses are no longer drawn; before, the annotation ran inline after its base.
  • Rows under a rowspan break across pages, so tables with spanning cells can take fewer pages and break in different places than in 1.24.0.
  • Solid text decorations are a tenth of the font size thick in whole pixels (they were 5.5%), and the overline stands on the ascent.
  • Annotations without an appearance stream are drawn by PdfToImage, PdfRenderer and PdfToHtml; 1.24.0 skipped them.
  • PdfPecker.Razor depends on Microsoft.AspNetCore.Components.Web 8.0.34, 9.0.23, 10.0.15 and 11.0.0, the November patches.

Output changes

Golden baselines changed:

  • features/text-decoration, features/text-styling, features/font-face-metrics, markdown/demo and markdown/report, and the fluent goldens text, extras and catalogue: only their solid underlines, overlines and line-throughs, now as thick and placed as in Chrome.
  • features/table-rowspan-breaks: spanning cells break across pages as in Chrome (3 pages instead of 4) and the rows beside a tall spanning cell share its height.
  • features/table-visibility-collapse: in case 4 the span's height is shared between its rows instead of all going to the last.

The new golden page complex/vertical-cjk adds a baseline and changes none.

Other documents change when they use what changed: solid text decorations, tables with rowspan, vertical text with CJK characters or images, Khmer, Myanmar, Sinhala or Tibetan text, <ruby>, images with min-width, max-width, min-height or max-height, flex rows with object-fit: cover images at a page end, percentage heights in flex items, and CSS gradients between translucent stops of different colours. Documents without device-cmyk(), PdfX or level A conformance are otherwise unchanged.

The manual for this version: https://pdfpecker.net/docs/

Full Changelog: v1.24.0...v1.25.0