[bug #63028] document nroff \o limitations in modern terminal emulators

[Dave]

Follow-up Comment #3, bug #63028 (project groff):

[comment #0 original submission:]
> (And maybe (3) that if they want to use \o for accented
> characters, there are more robust ways to achieve that.)

Nowadays, most of groff's Texinfo examples try to exhibit groff best
practices, but the manual does have an example (polished by bug #63002) that
uses \o to produce an accented character.

@Example
A caf\o
e\(aa
in Paris
    @result{} A café in Paris
@endExample

Despite this not being a good way in general to place diacritics on characters
(it's particularly ill suited to the letter i, which must shed its dot when it
acquires a diacritic), the advantage to using it in an example that many
readers will view on a terminal is that a terminal can give meaningful output
for it (albeit not through the \o mechanism but by using the appropriate
precomposed character).  This would not be the case with an example that
actually requires the overstrike to do its job, such as this style-nerdy one:

\[lq]I'm torn between US and UK punctuation styles\o
,\[rq]
she lamented.

However, taking context into account: this example isn't even trying to
illustrate the \o escape, but groff's ability to use newlines as
escape-sequence delimiters.  So maybe a different escape altogether would do
this job without the side effect of choosing between best-practice groff code
and terminal-displayable output (notwithstanding the fact that using newlines
as delimiters is certainly not a best practice itself.  But at least that is
discouraged in the very next sentence.  There's no comment on the
overstriking-to-apply-diacritics aspect of the example--and such a warning
would be out of place here, since the use of \o is not the point of this
section).

I don't have a suggestion offhand of a better escape for this; I'd need to
peruse the list of escapes that accept newlines as delimiters and choose one
that can produce output that would render well on a terminal.


    _______________________________________________________

Reply to this item at:

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

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