bug-groff
[Top][All Lists]
Advanced

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

[bug #58933] [PATCH] doc/groff.texi, man/groff.7.man: clarify descriptio


From: Dave
Subject: [bug #58933] [PATCH] doc/groff.texi, man/groff.7.man: clarify description of \&
Date: Mon, 10 Aug 2020 17:17:21 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0

URL:
  <https://savannah.gnu.org/bugs/?58933>

                 Summary: [PATCH] doc/groff.texi, man/groff.7.man: clarify
description of \&
                 Project: GNU troff
            Submitted by: barx
            Submitted on: Mon 10 Aug 2020 04:17:20 PM CDT
                Category: Core
                Severity: 3 - Normal
              Item Group: Documentation
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

On a suggestion from Peter Schaffter
(http://lists.gnu.org/archive/html/groff/2020-07/msg00100.html) that \& is
best described as "a zero-width, non-printing character" -- itself in reply to
my observation that groff's current term, "zero-width space," is a bit
misleading, especially as that's the name of a Unicode character (U+200B)
equivalent to groff's \: rather than its \& -- I created this patch
(originally posted at
http://lists.gnu.org/archive/html/groff/2020-08/msg00014.html) to update
groff's documentation accordingly.

Both target files have changed since I created the patch, but it still (as of
commit 4ce01df7) applies cleanly.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Mon 10 Aug 2020 04:17:20 PM CDT  Name: zwnpc.patch  Size: 3KiB   By:
barx
update description of \&amp; in doc/groff.texi and man/groff.7.man
<http://savannah.gnu.org/bugs/download.php?file_id=49650>

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58933>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

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