Skip to content

1.26.0 — Strikethroughs kept in redlines and tables

Choose a tag to compare

@capy-ai capy-ai released this 14 Nov 07:44
33fa2ea

Changes since 1.25.2:

  • Keep strikethroughs on pages that strike several lines of similar width, as tracked-changes documents do: the repeated-ruling filter only kept such a rule when it underlined the row it fits, so every one of these strikes was dropped as a table ruling. A rule that snugly strikes through one row is now kept, and the underlined row and the struck row are judged apart so neighbouring rows never combine into one owner (#663).
  • Keep strikethroughs on text inside a detected table: clearing the decorations of table text exists for underlines, which a cell's bottom border imitates, and no border runs through a cell's glyphs (#663).
  • Emit the strikethroughs recovered above as <s> without changing anything else on the page: run merging and heuristic table detection read them as before, and a word hyphenated across a line break inside a struck run rejoins across the reopened <s> tag (#663).
  • Read a TrueType subset with no cmap, no glyph names and no ToUnicode that comes from a core Windows font through the Windows variant of the standard glyph order, which the font's own advances choose: “N/A” no longer reads as —N/A“, company’s as company‘s or en dashes as œ. A glyph past the standard order that paints nothing but advances reads as a space, so Word's justified Arial lines no longer read U+FFFD between every word (#618).

API: TextItem::layout_strikeout (Rust), the strikeout layout heuristics read. It equals is_strikeout except on the strikethroughs recovered above. Rust literals of TextItem must include the new field. The Node, Python and WebAssembly bindings and the pdf2md --items-json fields are unchanged.

Release preparation: #665.

Full changelog