[groff] 01/28: ChangeLog: Clarify previous entries.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 99bacf4bbdaf7e324de75052a4d66cb4bf42d029
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Fri Aug 23 00:40:44 2024 -0500

    ChangeLog: Clarify previous entries.
---
 ChangeLog | 64 +++++++++++++++++++++++++++++++--------------------------------
 1 file changed, 32 insertions(+), 32 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 640a8bdd7..4ad19e5d0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,16 +1,15 @@
 2024-08-24  Deri James  <deri@chuzzlewit.myzen.co.uk>
 
-       Make gropdf compatible with IM 6(.9)
+       [gropdf]: Make compatible with ImageMagick (IM) < 7.0.
 
-       Peter Schaffter discovered some problems with recent
-       changes to gropdf and PDFPIC, they were not fully
-       compatible with ImageMagick 6.9 which is what he was
-       using. See here 
<https://lists.gnu.org/archive/html/groff/2024-08/msg00044.html>
+       Peter Schaffter discovered some problems with recent changes to
+       gropdf and the `PDFPIC` macro: they were not fully compatible
+       with ImageMagick 6.9, which he was using.  See <https://lists.
+       gnu.org/archive/html/groff/2024-08/msg00044.html>.
 
-       * src/devices/gropdf/gropdf.pl: One difference in IM 6 is
-       that an alpha channel of all zeroes meant the image was opaque,
-       but in 7 it is reversed and means the image is wholly
-       transparent.
+       * src/devices/gropdf/gropdf.pl: One difference in IM 6 is that
+       an alpha channel of all zeroes meant the image was opaque, but
+       in 7 it is reversed and means the image is wholly transparent.
 
        This change is documented here:-
 
@@ -18,39 +17,40 @@
 
        "Alpha
 
-       We support alpha now, previously opacity. With alpha, a value
+       We support alpha now, previously opacity.  With alpha, a value
        of 0 means that the pixel does not have any coverage information
-       and is transparent; i.e. there was no color contribution from any
-       geometry because the geometry did not overlap this pixel. A value
-       of QuantumRange means that the pixel is opaque because the geometry
-       completely overlapped the pixel. As a consequence, in version 7,
-       the PixelInfo structure member alpha has replaced the previous
-       opacity member. Another consequence is the alpha part of an sRGB
-       value in hexadecimal notation is now reversed (e.g. #0000 is fully
-       transparent)."
+       and is transparent; i.e. there was no color contribution from
+       any geometry because the geometry did not overlap this pixel.  A
+       value of QuantumRange means that the pixel is opaque because the
+       geometry completely overlapped the pixel.  As a consequence, in
+       version 7, the PixelInfo structure member alpha has replaced the
+       previous opacity member.  Another consequence is the alpha part
+       of an sRGB value in hexadecimal notation is now reversed (e.g.
+       #0000 is fully transparent)."
 
        This is now handled by gropdf.
 
-       There was an undocumented (I thought it came as part of perlmagick,
-       it doesn't) dependency on the module Image::ExifTool this is no
-       longer used by gropdf - so not required.
+       There was an undocumented (I thought it came as part of
+       perlmagick--it doesn't) dependency on the module
+       Image::ExifTool.  This is no longer used by gropdf, so not
+       required.
 
-       * tmac/pdfpic.tmac: Another issue was that identify sometimes
-       reports sizes for pdfs which do not match the page size, (it seems
-       to be attempting to report the size of the image embedded in the
-       pdf). For this reason pdfinfo is now used first on files, which
-       consistently reports the page size. There is a slight time penalty
-       since non-pdf files are subject to a (failed) pdfinfo run.
+       * tmac/pdfpic.tmac: Another issue was that identify(1) sometimes
+       reports PDF sizes that do not match the page size--it seems to
+       be attempting to report the size of the image embedded in the
+       PDF.  pdfinfo(1) is thus now used first on files, which
+       consistently reports the page size.  This imposes a slight time
+       penalty since non-PDF files endure a (failed) pdfinfo run.
 
 2024-08-24  Deri James  <deri@chuzzlewit.myzen.co.uk>
 
-       Handle preconv better
+       [gropdf]: Handle preconv better.
 
-       If preconv used, it should also be used when generating
+       If preconv is used, it should also be run when generating
        forward references.
 
-       * src/devices/gropdf/pdfmom.pl: add preconv (if requested)
-       to the pre-run which generates the pdf:bm strings.
+       * src/devices/gropdf/pdfmom.pl: Add preconv (if requested)
+       to the pre-run that generates the `pdf:bm` strings.
 
 2024-08-21  G. Branden Robinson <g.branden.robinson@gmail.com>
 
@@ -125,7 +125,7 @@
 
        * src/roff/troff/input.cpp (get_delimited_name, do_if_request)
        (read_drawing_command, read_drawing_command_color_arguments):
-       When complaining of mismatched or missing closing delimeter,
+       When complaining of mismatched or missing closing delimiter,
        report the identity of the delimiter we were expecting.
        * src/roff/troff/reg.cpp (alter_format): When complaining of
        invalid register format, list the valid ones.