[bug #62814] consolidate or distinguish tty.tmac and tty-char.tmac

[Ingo Schwarze]

Follow-up Comment #1, bug #62814 (project groff):

Arguably, the definitions in tty.tmac are of such a high quality that any user
of terminal output wants to use term unconditionally, and warnings about
characters in the input document that need any of these fallbacks would make
little sense.

Most of the fallbacks in tty-char.tmac, on the other hand, are arguably
desperate attempts to somehow render the respective characters even when good
renderings don't really exist, and most are of dubious or even poor quality. 
Some users might possibly prefer warnings about unavailable characters to poor
or cryptic renderings, and hence decide to not load tty-char.tmac, in
particular if they consider changing the input file to more gracefully render
to ASCII.

That said, while i see why some users might want to *not* load tty-char.tmac
for some uncommon purposes, personally i never felt a need to suppress its
loading for my purposes.  Quite to the contrary, it happened several times
that i simply forget loading it, resulting in badly degraded output.  So i
think most users would be better served by loading it by default.

If you want to be extra careful, you could leave these in their own file
though, such that people who want to scutinize a document for characters that
render badly to ASCII can more easily do so by disabling loading the file in
one way or another.


    _______________________________________________________

Reply to this item at:

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

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