[bug #55154] .tr has undocumented and inconsistent space-character restrictions

[Dave]

Follow-up Comment #8, bug #55154 (project groff):

Everything else I wanted to say (here and in bug #64337) I ended up talking
myself out of.  All I have left are two minor comments on the documentation
update.

[comment #6 comment #6:]
> > This feature replaces the odd-parity tr mapping trick 

"replaces" implies that the odd-parity trick has gone away.  Maybe "augments"
or "parallels"?

> > Translation of a character to \~ is unnecessary.

This seems unnecessarily opinionated for technical documentation.  Arguably
all translations are unnecessary.  But they're a useful tool, allowing you to
(1) simplify or make more legible your input, or (2) treat certain characters
conditionally (e.g. based on the output device).  I'm not sure it's fair to
characterize mapping to \~ as any more or less necessary than mapping to any
other character.

The goal presumably being to steer users away from a mapping that may be
deprecated, saying so directly probably serves the reader better, e.g.:
"Translation of a character to \~ may be deprecated in a future release."


    _______________________________________________________

Reply to this item at:

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

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