[bug #66040] groff no longer warns about unrecognized .hcode input

URL: Summary: groff no longer warns about unrecognized .hcode input Group: GNU roff Submitter: barx Submitted: Mon 29 Jul 2024 02:07:31 AM CDT Category: Core S

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Update of bug #66040 (group groff): Summary: groff no longer warns about unrecognized .hcode input => [troff] no longer warns about unrecognized .hcode input ___ Follow-up Comment #1: Goodness. It's against my ethos to ki

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Update of bug #66040 (group groff): Status:None => Confirmed Assigned to:None => gbranden ___ Follow-up Comment #2: Some "improvement"! :-

[bug #66038] [troff] want "invalid line length" diagnostic to quote user input

Follow-up Comment #3, bug #66038 (group groff): Right. I'll clarify that my complaint isn't "the diagnostic won't parrot my input back to me", it's "the diagnostic is emitting a number that seems--to a user not versed in groff internals--unconnected to anything in input." Two possible ways of ad

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Follow-up Comment #3, bug #66040 (group groff): [comment #2 comment #2:] > Some "improvement"! :-O I'm sure that commit made many improvements. Sometimes taking three steps forward also involves taking one back. ___ Reply to this item a

[bug #65955] [troff] enable "input" warning category by default and add one-off alert

Follow-up Comment #3, bug #65955 (group groff): My recent citing of bug #42870 in another bug report makes me realize it's a blocker for this one. As long as requests .hcode and .hw require any Latin-1 Supplement characters in their arguments to be specified using 8-bit characters (by not recogni

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Update of bug #42870 (group groff): Status:None => Need Info ___ Follow-up Comment #5: [comment #0 original submission:] > `.hcode' and `.hw' are limited to raw 8bit characters. This do

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Follow-up Comment #6, bug #42870 (group groff): (at least for `hcode`) ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Follow-up Comment #7, bug #42870 (group groff): In case anyone's curious, here's a demonstration of "raw 8-bit characters" working with `hw`. I know that's not what's complained about but since I'm digging into this, I thought I would share it. $ cat EXPERIMENTS/kindergarten-utf8.groff .if r HW

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Update of bug #42870 (group groff): Status: Need Info => Unreproducible Assigned to:None => carstenkunze ___ Follow-up Comment #8: I cannot reproduce the

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Follow-up Comment #9, bug #42870 (group groff): The example in comment #8 works for me with _groff_ 1.22.4 and _groff_ 1.23.0. Possibly Werner fixed this a long time ago? ___ Reply to this item at:

[bug #42870] `.hcode' and `.hw' are limited to raw 8bit characters but should accept any characters entities.

Follow-up Comment #10, bug #42870 (group groff): The example in comment #8 works for me with _groff_ 1.22.3 as well. That was released in November 2014, a mere four months after the mailing list thread linked in comment #1. It's possible Werner was mistaken, and he misremembered a feature as mis

[bug #42870] [troff] `.hcode' and `.hw' are limited to ordinary characters

Update of bug #42870 (group groff): Status: Unreproducible => Invalid Assigned to:carstenkunze => gbranden Open/Closed:Open => Closed Summary: `.hco

[bug #42870] [troff] `.hcode' and `.hw' are limited to ordinary characters

Update of bug #42870 (group groff): Status: Invalid => None Open/Closed: Closed => Open ___ Follow-up Comment #12: [comment #8 comment #8

[bug #66040] [troff] no longer warns about unrecognized .hcode input

Update of bug #66040 (group groff): Status: Confirmed => In Progress ___ Follow-up Comment #4: I have a fix. diff --git a/src/roff/troff/input.cpp b/src/roff/troff/input.cpp index d0ef4a0f1..11