groff-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[groff] 01/02: ChangeLog: Clarify item.


From: G. Branden Robinson
Subject: [groff] 01/02: ChangeLog: Clarify item.
Date: Mon, 4 Mar 2024 17:38:32 -0500 (EST)

gbranden pushed a commit to branch master
in repository groff.

commit 4dfbb4b79b4765150b67548e4790eae0ff57e9a3
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Mon Mar 4 15:33:40 2024 -0600

    ChangeLog: Clarify item.
---
 ChangeLog | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index f6e0587ea..f69ff3dc8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -5,7 +5,7 @@
        * tmac/pdf.tmac (pdf:lookup): Given an argument, search defined
        bookmark tags for a match and return one (if found) in the
        string `pdf:lookup-result`, which is defined but empty if there
-       is no match.  Previously (and, actually, still--see below),
+       is no match.  Previously (and, for mom(7), still--see below),
        lookups were O(1) because strings named `pdf:look($TAG_NAME)`
        were defined.  The speed was great but unfortunately, in
        practical use, tags often got *roff escape sequences stuck into
@@ -23,7 +23,7 @@
        through a string, scrubbing it of `\%` escape sequences.  Much
        more exotic things could be placed in bookmark tags; we were
        fortunate that man page cross references tend to stick to ASCII,
-       plus `\%` to suppress hyphenation.  But that's only suitable for
+       plus `\%` to suppress hyphenation.  But that's suitable only for
        man page references; if we want taggable (sub)section headings,
        like groff_mmse(7)'s "Se ocksÄ", we need strings, not just valid
        groff identifiers.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]