[bug #66009] [troff] accepts `|` as operand delimiter, but should not

Update of bug #66009 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #66006] [grog] Identifies .TS .TH .TE as a -man document

Update of bug #66006 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 __

[bug #65138] [troff] `device` request silently fails before first page begins

Update of bug #65138 (group groff): Status: In Progress => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #5: commit 5be9a9cd0e177d9

[bug #64301] [troff] susceptible to integer overflow

Update of bug #64301 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #7: commit a3e0a4fe337a148

[bug #61453] want native mechanism for continuous (non-paginated) rendering

Follow-up Comment #11, bug #61453 (group groff): [comment #10 comment #10:] > [comment #7 comment #7:] > > I'm a little nervous of meddling with the semantics of a > > negative page length given the potential for interaction with > > negative vertical drawing positions. > > There seem to be (at l

[bug #65099] 1.24.0 release goals

Follow-up Comment #5, bug #65099 (group groff): [comment #4 comment #4:] > I submit bug #63827 as something that should be addressed in some manner before release, even if only in the form of a stopgap like resyncing groff's pdfmark subtree with the substantially updated code upstream. It's on th

[bug #65108] [troff] support construction of general file name request arguments

Follow-up Comment #8, bug #65108 (group groff): [comment #7 comment #7:] > One additional comment on the proposal: > > [comment #3 comment #3:] > > Only codes in the range 00-1F and 80-FF are accepted in > > [`\[u00XX]`] syntax; those in the range 20-7F are ignored with a > > diagnostic advising

[bug #65108] [troff] support construction of general file name request arguments

Follow-up Comment #9, bug #65108 (group groff): [comment #5 comment #5:] > So I'm not sure whether or not you advocate retaining soelim's current escape mechanism. Maybe you're not yet either. It's a question that tempts me to dither. > My suggestion in comment #2 that support for soelim's es

[bug #66027] [soelim] stop requiring spaces to be backslash-escaped, and strip leading double quote

URL: Summary: [soelim] stop requiring spaces to be backslash-escaped, and strip leading double quote Group: GNU roff Submitter: gbranden Submitted: Fri 26 Jul 2024 03:48:54 AM UTC

[bug #66027] [soelim] stop requiring spaces to be backslash-escaped, and strip leading double quote

Update of bug #66027 (group groff): Depends on: => bugs #65108 ___ Reply to this item at: ___ Message

[bug #66000] [mm] early .CS call makes top page margin wrong thereafter

Follow-up Comment #3, bug #66000 (group groff): [comment #1 comment #1:] > I was planning to add an `AFX` macro to permit override of the formatting of the "affiliated firm" header. Historical practice is crazily divergent, being an obvious site for the "[https://www.youtube.com/watch?v=4NomQYQK

[bug #63018] [PATCH] make glyphs in ZD font accessible via their Unicode spellings

Follow-up Comment #36, bug #63018 (group groff): [comment #34 comment #34:] > [comment #33 comment #33:] > > This started off as a simple request to give access to Dingbats > > glyphs via their \[u] names... and then wandered! > > I agree, the solution you outline will resolve this bug's compl

[bug #57506] Suspicious "slant" values in devps/TI, devlbp/HI, devlbp/HBI

Update of bug #57506 (group groff): Assigned to:gbranden => None ___ Follow-up Comment #17: Unassigning from self; I don't have answers to Dave's questions in comment #16.

[bug #55154] [troff] `tr` request has undocumented and inconsistent space-character restrictions

Update of bug #55154 (group groff): Status: Need Info => Confirmed Assigned to:barx => None Summary: .tr has undocumented and inconsistent space-character restrictions => [troff] `tr`

[bug #55154] [troff] `tr` request has undocumented and inconsistent space-character restrictions

Update of bug #55154 (group groff): Severity: 2 - Minor => 3 - Normal Item Group: Incorrect behaviour => Documentation ___ Follow-up Comment #18: Re-"item group"ing as