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

[Dave]

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

[comment #1 comment #1:]
> So i think most users would be better served by loading it by default.

That's my gut feeling, though as someone who doesn't use most of this file's
character palette, I defer to the judgment of more experienced users.  In
general it just seems more user-friendly to render characters in a suboptimal
way than to throw warnings and leave those spots empty.

> 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.

Giving power users that option would be good.  One possible mechanism would be
wrapping the lower-quality definitions in an .if block, in such a way that a
user defining a certain register on the command line would cause that block to
be skipped.  Then it wouldn't matter as much which file they lived in.

There could be separate registers to control each set of fallbacks, in fact,
in case a user wants to disable them all, such as for a testing scenario of
the type Branden alluded to in the email thread.


    _______________________________________________________

Reply to this item at:

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

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