No changes entry is lost (as far as I see).

I only reformatted the changes entry dated "Mon Jul 18 07:28:54 UTC 2022" to have its lines not longer than 68 characters.

Additionally I added some more information that belongs to this changes entry about the possible Tesseract OCR support in Ghostscript which was never built for openSUSE because 'configure' automatically disabled Tesseract OCR support in Ghostscript because currently there is no C++ compiler in the Ghostscript build system.

Therefore that changes entry which talked about Tesseract OCR support in Ghostscript was wrong (or at least misleading) because we never built it which is why I enhanced that changes entry by the following two parts:

"Mainly due to time constraints, we only support including Tesseract from source included in our release packages, and not linking to Tesseract/Leptonica shared libraries. Whether we add this capability will be largely dependent on community demand for the feature. See Enabling OCR at https://www.ghostscript.com/ocr.html for more details."

and

"Configure --without-tesseract because this requires C++ (it might be added if Tesseract support in Ghostscript is needed)."

plus in ghostscript.spec

"%configure ... --without-tesseract"

to make it clear and obvious that (at least currently) Ghostscript is built without Tesseract OCR support.

FYI regarding "why not 'just build' Ghostscript with Tesseract OCR support":

As long as this is not really needed (business case) I do not want to have any more piece of foreign source code (here "Tesseract from source included in our release packages") in Ghostscript because each piece of foreign source code in a package is a maintenance burden: Assume there is a severe (security) bug in Tesseract then we have its sources duplicated (in possible different versions) so we have duplicated maintenance efforts and the maintenance team must somehow know (and maintain) that we have duplicated sources.