URL:
  <http://savannah.gnu.org/bugs/?50898>

                 Summary: groff_char(7) manual: improve description of ASCII
characters that do not render as themselves
                 Project: GNU troff
            Submitted by: schwarze
            Submitted on: Sat 29 Apr 2017 06:57:30 PM UTC
                Severity: 3 - Normal
              Item Group: Wishlist
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None

    _______________________________________________________

Details:

This patch improves the section "7-bit Character Codes 32126" in the
groff_char(7) manual in five respects:

1. Add clarity by giving the Unicode numbers for each output glyph.

2. Add even more clarity by also giving the character names that can be used
to explicitly request each specific glyph, rather than simply typing some
ASCII character.

3. Correct the output glyph for the input "'".  In a manual page, "'" does not
render as a right single quotation mark (Unicode u2019), so we really need
\[cq] here.

4. Add a sentence explaining that in typography, the right single quotation
mark is usually used to represent the punctation apostrophe as well, to avoid
misleading people into writing "don\(aqt".

5. Recommend \(mi if people explicitly want a minus sign rather than \-,
because in some macro sets, \- may render as an ASCII hyphen-minus and *not*
as a minus sign.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Sat 29 Apr 2017 06:57:30 PM UTC  Name: groff_char.patch  Size: 2kB   By:
schwarze

<http://savannah.gnu.org/bugs/download.php?file_id=40534>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50898>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/


_______________________________________________
bug-groff mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-groff

Reply via email to