Fix fpdf text mode in multi-page renderer; add v17.2.0 release notes

The previous fix (e62e73e4) only corrected text_rendering_mode →
text_mode in the single-page Fpdf2PdfRenderer, but the main OCR
pipeline uses Fpdf2MultiPageRenderer which still had the old
attribute name. Since fpdf2 has no text_rendering_mode property,
setting it silently created a no-op attribute while text_mode stayed
at FILL — so 3 Tr (invisible text) was never emitted.

Fixes #1631, #1632
This commit is contained in:
James R. Barlow
2026-02-10 14:12:49 -08:00
parent e62e73e441
commit 5c83dab8a7
2 changed files with 14 additions and 2 deletions
+12
View File
@@ -26,6 +26,18 @@ official when it's tagged and posted to PyPI.
:::
## v17.2.0
- Fixed OCR text layer being visible instead of invisible due to incorrect fpdf2
text rendering mode attribute. This caused OCR text to appear when images were
removed from the PDF. {issue}`1631`
- Fixed OCR text layer misalignment with non-zero mediabox origins, which
affected cropped PDFs and JSTOR PDFs generated by iText. The ``--redo-ocr``
mode would shift text vertically on these files. {issue}`1630`
- Fixed Ghostscript rasterization failure with very low DPI values (below 10).
OCRmyPDF now renders at a minimum of 10 DPI and resizes the output to match
the originally requested dimensions. {issue}`1612`
## v17.1.0
- Added `--tagged-pdf-mode` to allow skipping the TaggedPDF error message, if desired.