Update of bug #67252 (group groff):

                  Status:                    None => Need Info

    _______________________________________________________

Follow-up Comment #4:

Beyond what Dave and I discussing with our ambitions in refactoring
"fallbacks.tmac" and the device-specific macro files, I'm not sure there is a
correct way to handle this problem.

One of the points of _groff_char(7) is to exhaustively enumerate _groff_'s
built-in special character repertoire.  If a device can't cope with that, it's
the device's problem.

Tables overrunning because a fallback is defined that makes an unavailable
character "too wide", well, that's something the user is going to have to live
with.

Dave, do we have another ticket that discusses the
`tty*use-semantic-fallbacks` refactor, or whatever I was calling it X months
ago?


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to