From 6707ad427a808505ccf4512917db553330db6858 Mon Sep 17 00:00:00 2001 From: "James R. Barlow" Date: Thu, 4 Oct 2018 01:21:17 -0700 Subject: [PATCH] v7.2.0 release notes --- docs/release_notes.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/release_notes.rst b/docs/release_notes.rst index c654156c..968adced 100644 --- a/docs/release_notes.rst +++ b/docs/release_notes.rst @@ -13,6 +13,26 @@ Note that it is licensed under GPLv3, so scripts that ``import ocrmypdf`` and ar find: [^`]\#([0-9]{1,3})[^0-9] replace: `#$1 `_ + +v7.2.0 +------ + +**About lossy JBIG2** + +A user reported that ocrmypdf was in fact using JBIG2 in **lossy** compression mode. This was not the intended behavior. Users should `review the technical concerns with JBIG2 in lossy mode `_ and decide if this is a concern for their use case. + +JBIG2 lossy mode does achieve higher compression ratios than any other monochrome compression technology; for large text documents the savings are considerable. JBIG2 lossless still gives great compression ratios and is a major improvement over the older CCITT G4 standard. + +Only users who have reviewed the concerns with JBIG2 in lossy mode should opt-in. As such, lossy mode JBIG2 is only turned on when the new argument ``--jbig2-lossy`` is issued. This is independent of the setting for ``--optimize``. + +Users who did not install an optional JBIG2 encoder are unaffected. + +(Thanks to user 'bsdice' for reporting this issue.) + +**Other issues** + +- Fixed handling of Tesseract 4.0-rc1 which now accepts invalid Tesseract configuration files, which broke the test suite. + v7.1.0 ------