tag 551111 + upstream fixed-upstream
thanks

This bug was found and corrected independently.  The fix is expected in
the groff 1.23 release.

commit 2bd31bb3f2de8e8ff21540ca7c247025903d8acc
Author: G. Branden Robinson <g.branden.robin...@gmail.com>
Date:   Thu Feb 13 20:25:08 2020 +1100

    groff(7): Fix style and correctness issues.

    * Add a sentence calling out the characters (key engravings) that
      most often come to grief on output devices.  Add cross-reference to
      groff_char(7).
    * Drop language later on describing what the ' and ` characters do when
      "unescaped", which was incompletely presented, not done for other
      characters, and was erroneously presented for ' in the first place.

    * Follow the advice we give; in literal input examples, use \[ha]
      instead of ^, and \[ti] instead of ~.

    * Replace many uses of \[cq] with \[aq] when the latter is what is
      meant: in input sequences, the .tl example, and a page-private macro
      definition for documenting escape sequences.
    * Delete unused 'escq' macro.
    * Don't refer to "'" as a "single quote" in an input context.  It's the
      apostrophe in all modern character encodings.
    * Mention that how the apostrophe is rendered depends on the output
      device.

    * Recast discussion of the space character in input.  Rewrite for
      clarity.  Discuss how spaces are treated when filling and/or
      adjustment are enabled.
    * Add \0 to the list of "spaces of definite width".  Hat tip to Dave
      Kemper for prompting this.
    * Add mention of the nonbreaking space escape \~.

    * Note end-of-sentence detection in discussion of spaces and newlines.

    * Drop mentions of ASCII; as noted in recent discussions of the \[oq]
      escape and Latin-1 encoding (-Tlatin1), most people who purport to
      viewing nroff output on an ASCII device probably are not.  It's been a
      UTF-8 world in *nix land for a long time now; mentions of ASCII should
      be confined to specialized situations.

    * More closely align the names of characters represented by the \[de]
      and \[rs] escapes with their Unicode codepoint descriptions.  More
      work could be done on this page in this respect.

    * Add \[ha] and \[ti] to the list of character escapes.

    * Correct erroneous presentation of a \´ (backslash, acute accent)
      escape.  Once again, an apostrophe is meant.

    * Fix minor formatting inconsistencies (not visible on output).

    Misinformation about acute accents and apostrophes in this page was
    presented with such unrelenting dedication that I have to wonder if it
    was originally written by someone using a German keyboard with the acute
    accent (´) key remapped to apostrophe (').  See
    <https://www.cl.cam.ac.uk/~mgk25/ucs/apostrophe.html>.

Regards,
Branden

Attachment: signature.asc
Description: PGP signature

Reply via email to