bug-groff
[Top][All Lists]
Advanced

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

[bug #60836] Improve documentation of output-comparison operator


From: Dave
Subject: [bug #60836] Improve documentation of output-comparison operator
Date: Sat, 19 Mar 2022 13:32:42 -0400 (EDT)

Follow-up Comment #11, bug #60836 (project groff):

[comment #10 comment #10:]
> The following commit is pending; please let me know what you think.

Er, I failed to do that before this went to press (as commit fbdfd927
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=fbdfd927>), but I think
it's a great set of refinements and clarifications.

If I had to quibble, I'd wonder whether, in a coding rather than a typesetting
context, "neutral apostrophes" is a better descriptor than "single quotes." 
Programmers are certainly more used to calling them single quotes; and even to
noncoders, either term should be understandable.  Also, as delimiters for
strings, they function semantically more as quotes than as apostrophes.  At
this point in the manual, there shouldn't be reason to worry that users might
interpret "single quotes" as U+2018 and U+2019, since it has previously
established that groff code is limited to Latin-1.


    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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