Update of bug #67252 (group groff):

                  Status:               Need Info => Rejected
             Assigned to:                    None => gbranden
                 Summary: groff_char.7: some tables too wide in ascii or
latin1 output => groff_char(7): some tables too wide on 'ascii' or 'latin1'
output devices

    _______________________________________________________

Follow-up Comment #17:

There's been no feedback from Bjarni despite his activity in other _groff_
tickets, so I conclude that we're not going to hear from him.

[comment #13 comment #13:]
>>> while some tty-char.tmac fallbacks are useful outside
>>> terminal output, the current infrastructure effectively
>>> supports them only when running nroff.
>> 
>> Join me in welcoming bug #67356 to the world.
> 
> Excellent.  The proposal there is (I paraphrase) "let users of any output
> driver opt in to semantic fallbacks".
> 
> Separate issue #1: There may be some fallbacks in "tty-char.tmac" that should
> remain confined to the _grotty_ output driver's supporting macro file.
> That's essentially bug #62814.
> 
> Separate issue #2: We should warn (or be configurably able to) when unfilled
> lines are overset.  That's bug #66977.
> 
> Separate issue #3: _groff_char_(7) should be revised to present glyph tables
> that don't overset when semantic fallbacks are used.  If that's all that
> remains of this ticket, I am inclined to close it as "Rejected".
> 
> Is the foregoing a fair redrawing of the multifarious issues arising from
> comment #0?

Dave and I think so.

Closing this ticket as "Rejected".  See above for surviving issues.


    _______________________________________________________

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