[bug #66174] [mdoc] wrong interpretation of '.Bl ... -width "long string"'

Follow-up Comment #1, bug #66174 (group groff): [comment #0 original submission:] > N.B. What integer's value is saturated? (the name of the integer variable?) 1. The numeric expression parser doesn't know. That information is not passed down through the function calls that implement it. Not

[bug #52463] anything that talks to standard error should identify itself

Follow-up Comment #8, bug #52463 (group groff): commit 3accb8772240c4a604527d50d78c74147062b51f Author: G. Branden Robinson Date: Wed Sep 11 01:55:09 2024 -0500 [pre-grohtml]: Improve diagnostic messages. * src/preproc/html/pre-html.cpp: Improve diagnostic message handling.

[bug #66112] Map Latin-1 Supplement character hyphenation codes to their base-character equivalents

Update of bug #66112 (group groff): Status:None => Need Info Assigned to:None => barx ___ Follow-up Comment #1: Dave, would you be will

[bug #66103] manpage-10n project: issues in man pages

Update of bug #66103 (group groff): Summary: Issues in man pages => manpage-10n project: issues in man pages ___ Reply to this item at: ___

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #1, bug #66103 (group groff): At 2024-08-18T13:53:13-0400, Helge Kreutzmann wrote: > Please note: I know you are not following traditional man rules any > more, I dispute that. I think groff's man pages are as faithful to the format and conventions established in the Seventh Ed

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #2, bug #66103 (group groff): ___ Reply to this item at: ___ Message sent via Savannah https://savannah.gnu.org/ signature.asc Desc

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #3, bug #66103 (group groff): Looks like Savane got angry with me. Here's what I *tried* to reply with via email: Subject: Re: [bug #66103] manpage-10n project: issues in man pages [self-follow-up] I had a wordo here. At 2024-09-11T04:33:41-0400, G. Branden Robinson wrote:

[bug #66187] [troff] permit control over flushing of output file state

Update of bug #66187 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Follow-up Comment #4: This is one stubborn so

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #4, bug #66103 (group groff): >> Man page: soelim.1 >> Issue 1: I<\\%soelim> → B<\\%soelim> >> Issue 2: I<\\%troff> → .MR \\%troff 1 >> >> "I<\\%soelim> is I required for I<\\%troff> to source files." > As this is the very next sentence, another cross reference here would be

[bug #66112] Map Latin-1 Supplement character hyphenation codes to their base-character equivalents

Follow-up Comment #2, bug #66112 (group groff): [comment #1 comment #1:] > Dave, would you be willing to prepare an appropriate patch to "tmac/en.tmac"? I'll do better than that--I'll prepare _two_. The first contains only those characters that appear in English words, as defined by the SCOWL wo

[bug #66112] Map Latin-1 Supplement character hyphenation codes to their base-character equivalents

Update of bug #66112 (group groff): Status: Need Info => None Assigned to:barx => None ___ Reply to this item at:

[bug #66112] [l10n:english] map Latin-1 Supplement character hyphenation codes to base-character equivalents

Update of bug #66112 (group groff): Status:None => Confirmed Summary: Map Latin-1 Supplement character hyphenation codes to their base-character equivalents => [l10n:english] map Latin-1 Supplement character hyphenation codes to

[bug #65099] 1.24.0 release goals

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

[bug #66103] manpage-10n project: issues in man pages

Follow-up Comment #5, bug #66103 (group groff): ___ Reply to this item at: ___ Message sent via Savannah https://savannah.nongnu.org/ signature.as