[groff] 06/14: ChangeLog: Wrap lines at 72 columns.

[G. Branden Robinson]

gbranden pushed a commit to branch master
in repository groff.

commit 059f2d85e43d180eb52f470801e82327716cfbf7
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sat Apr 20 14:31:11 2024 -0500

    ChangeLog: Wrap lines at 72 columns.
    
    ...per the editor aids at the end of the file.
---
 ChangeLog | 26 ++++++++++++++------------
 1 file changed, 14 insertions(+), 12 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index c65db2611..40367295a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -2,10 +2,11 @@
 
        [gropdf] Handle both types in one document.
 
-       The different format of font described in previous commit fails if
-       document contains fonts of both formats. The reason is because the
-       regexes included the /o flag (compile once) for speed, but if the
-       format changed (from RD to -|) in a different font, parsing failed.
+       The different format of font described in previous commit fails
+       if document contains fonts of both formats. The reason is
+       because the regexes included the /o flag (compile once) for
+       speed, but if the format changed (from RD to -|) in a different
+       font, parsing failed.
 
        Now the regexes are compiled once for each font.
 
@@ -16,15 +17,16 @@
 
        [gropdf] Improve font parsing.
 
-       The usual (for fontforge converted ttf fonts) is to use the RD, ND
-       and NP operators within charstring definitions, however these are
-       just named in the private subrs dictionary so could be assigned
-       any name.
+       The usual (for fontforge converted ttf fonts) is to use the RD,
+       ND and NP operators within charstring definitions, however these
+       are just named in the private subrs dictionary so could be
+       assigned any name.
 
-       A debian .pfb version of a google .ttf font (which has not passed
-       through fontforge) used -| |- and | as the 3 equivalent. In
-       addition it used a different lenIV value for the eexec encryption (4)
-       and the charstring encryption (0) (didn't know you could do that).
+       A debian .pfb version of a google .ttf font (which has not
+       passed through fontforge) used -| |- and | as the 3 equivalent.
+       In addition it used a different lenIV value for the eexec
+       encryption (4) and the charstring encryption (0) (didn't know
+       you could do that).
 
        * src/devices/gropdf/gropdf.pl: Make RD, ND and NP variables set
        from parsing the private subrs. Honour lenIV=0 when encrypting