v14.4.0 docs and release notes

ocrmypdf · Aug 12, 2023 · a371655 · a371655
1 parent a6ce35b
commit a371655
Show file tree

Hide file tree

Showing 2 changed files with 27 additions and 0 deletions.
diff --git a/docs/cookbook.rst b/docs/cookbook.rst
@@ -372,3 +372,17 @@ Some users may consider enabling lossy JBIG2. See: :ref:`jbig2-lossy`.
 
     Image processing and PDF/A conversion can also introduce lossy transformations
     to your PDF images, even when ``--optimize 1`` is in use.
+
+
+Digitally signed PDFs
+=====================
+
+OCRmyPDF cannot preserve digital signatures in PDFs and also add to OCR to them.
+By default, it will refuse to modify a signed PDF regardless of other settings. You can
+override this behavior with ``--invalidate-digital-signatures``; as the name suggests,
+any digital signatures will be invalidated.
+
+OCRmyPDF cannot open documents that are encrypted with a digital certificate.
+
+Versions of OCRmyPDF prior to 14.4.0 would invalidate existing digital signatures
+without warning.
diff --git a/docs/release_notes.rst b/docs/release_notes.rst
@@ -28,6 +28,19 @@ tagged yet.
 
 .. |OCRmyPDF PyPI| image:: https://img.shields.io/pypi/v/ocrmypdf.svg
 
+v14.4.0
+=======
+
+-  Digitally signed PDFs are now detected. If the PDF is signed, OCRmyPDF will
+   refuse to modify it. Previously, only encrypted PDFs were detected, not
+   those that were signed but not encrypted. :issue:`1040`
+-  In addition, `--invalidate-digital-signatures` can be used to override the
+   above behavior and modify the PDF anyway. :issue:`1040`
+-  tqdm progress bars replaced with "rich" progress bars. The rich library is
+   a new dependency. Certain APIs that used tqdm are now deprecated and will
+   be removed in the next major release.
+-  Improved integration with GitHub Releases. Thanks to @stumpylog.
+
 v14.3.0
 =======