[bug #66052] [troff] possible 1-byte stack and heap overruns

Follow-up Comment #2, bug #66052 (group groff): Hi Lukas, I believe your first case is indeed a bug, though a relatively pathological case. Here's the ChangeLog entry I have pending for it. 2024-08-07 G. Branden Robinson

[bug #66052] [troff] possible 1-byte stack overwrite, heap overread

Update of bug #66052 (group groff): Summary: [troff] possible 1-byte stack and heap overruns => [troff] possible 1-byte stack overwrite, heap overread ___ Reply to this item at:

[bug #66052] [troff] possible 1-byte stack overwrite, heap overread

Follow-up Comment #3, bug #66052 (group groff): Confirmed the second case too. 2024-08-07 G. Branden Robinson [troff]: Fix Savannah #66052 (2/2). * src/roff/troff/input.cpp (temp_iterator::temp_iterator): Prevent potential heap overreads. Ensure that temporary

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

Update of bug #65955 (group groff): Status:None => Rejected Assigned to:None => gbranden Open/Closed:Open => Closed __

[bug #59397] [troff] want English hyphenation codes for Latin-1 Supplement characters

Follow-up Comment #11, bug #59397 (group groff): One step remains for this: see http://lists.gnu.org/r/groff/2024-08/msg9.html ___ Reply to this item at: __

[bug #59434] doc/groff.texi: document .if / .ie interaction more clearly

Update of bug #59434 (group groff): Status:None => Need Info Assigned to:None => barx ___ Follow-up Comment #6: Waiting on Dave to find

[bug #65246] [grops] download file does not handle .pfa file names that contain spaces

Update of bug #65246 (group groff): Summary: [grops] download file does not handle .pfa filenames which contain spaces => [grops] download file does not handle .pfa file names that contain spaces ___ Reply to this item at:

[bug #64484] [troff] \X escape sequence should read its argument in copy mode

Update of bug #64484 (group groff): Summary: [troff] .device and \X don't behave the same => [troff] \X escape sequence should read its argument in copy mode ___ Follow-up Comment #12: [comment #11 comment #11:] > Postponi

[bug #66054] [troff] permit special characters as source hyphenation codes

Update of bug #66054 (group groff): Status: Fixed => In Progress Open/Closed: Closed => Open ___ Follow-up Comment #2: This wasn't fully baked

[bug #66051] [troff] permit special characters to have bespoke hyphenation codes

Update of bug #66051 (group groff): Status:None => Postponed ___ Follow-up Comment #7: Rut-roh, Raggy. So, yeah, let's put in the missing bits. diff --git a/src/roff/troff/input.cpp b/

[bug #42870] [troff] revise hyphenation code management

Follow-up Comment #15, bug #42870 (group groff): This turns out to require rearchitecting the `symbol` class and things that use it. See bug #66051. It's hard. ___ Reply to this item at: ___

[bug #66054] [troff] permit special characters as source hyphenation codes

Follow-up Comment #3, bug #66054 (group groff): [comment #2 comment #2:] > 2. `.hcode \['a] \['a]` should have altered `\['a]`'s hyphenation code. I might be misunderstanding the semantics of assigning a character's hcode to itself. I understood it to mean "make this character eligible for hyph