From 1926ab41868ef780b0abcb530399e7e3a04cd2d6 Mon Sep 17 00:00:00 2001 From: DRC Date: Mon, 14 Nov 2022 16:31:41 -0600 Subject: [PATCH] ChangeLog.md: Multi-precision feature wordsmithing - Because of b5a9ef64ea299423b7fb46c47f4a70697a442dd4, "by default" is no longer applicable. (12-bit-per-component JPEG support is now part of the core libjpeg-turbo functionality and cannot be disabled.) - Change awkward "can be used to enable the creation of" to less awkward "can be used to create". --- ChangeLog.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ChangeLog.md b/ChangeLog.md index 9f933826..89778239 100644 --- a/ChangeLog.md +++ b/ChangeLog.md @@ -4,7 +4,7 @@ ### Significant changes relative to 2.1.4: 1. 12-bit-per-component JPEG support is now included in the libjpeg API -library, cjpeg, djpeg, and jpegtran by default: +library, cjpeg, djpeg, and jpegtran: - The existing `data_precision` field in `jpeg_compress_struct` and `jpeg_decompress_struct` has been repurposed to enable the creation of @@ -15,8 +15,8 @@ JPEG image is being decompressed. `jpeg_crop_scanline()`, and `jpeg_read_raw_data()` provide interfaces for compressing from/decompressing to 12-bit-per-component uncompressed image buffers. - - A new cjpeg command-line argument (`-precision`) can be used to enable -the creation of 12-bit-per-component JPEG images. (djpeg and jpegtran handle + - A new cjpeg command-line argument (`-precision`) can be used to create +a 12-bit-per-component JPEG image. (djpeg and jpegtran handle 12-bit-per-component JPEG images automatically.) Refer to [libjpeg.txt](libjpeg.txt) and [usage.txt](usage.txt) for more