[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #23, bug #66675 (group groff): The pushed version differs slightly from the comment #14 version: in comment #14, the second parameter of valid_unicode_code_sequence() was changed from "errbuf" to a null pointer. Is this difference intentional? In fact, by making it a null point

[bug #57556] [troff] enforce left and right minimums as required by hyphenation patterns

Follow-up Comment #13, bug #57556 (group groff): [comment #12 comment #12:] > I did read through #55070 and saw nothing that addressed the idea of > separating pattern minimums from user minimums. By my reading, it concerned > only separating the beginning and ending minimums from each other, an

[bug #44018] [PATCH] gtroff hangs in environment::possibly_break_line with -mja

Follow-up Comment #7, bug #44018 (group groff): Sharing an issue that I think may be related. When setting output lines of mainly or exclusively CJK scripts as opposed to Western ones, because hyphenation is disabled and word spaces are less common or, in some cases, unused, I think warnings in t

[bug #66919] [troff] behavior change in some .hcode calls when a special character is the first argument

Update of bug #66919 (group groff): Status: Need Info => None Assigned to:barx => None ___ Follow-up Comment #18: [comment #16 comment #16:] > Follow-up Comment #14, bug #669

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #24, bug #66675 (group groff): [comment #23 comment #23:] > The pushed version differs slightly from the comment #14 version: in comment > #14, the second parameter of valid_unicode_code_sequence() was changed from > "errbuf" to a null pointer. Is this difference intentional? Y

[bug #66931] [tbl] writes line number "1" wrongly in many `lf` requests since commit 25ef9f6bda

Update of bug #66931 (group groff): Summary: [tbl] writes line number "1" in every `lf` request since commit 25ef9f6bda => [tbl] writes line number "1" wrongly in many `lf` requests since commit 25ef9f6bda ___ Reply to thi

[bug #66905] [PATCH] Increase Unicode coverage by scaling back workaround for bug #63332

Update of bug #66905 (group groff): Status:None => In Progress Assigned to:None => gbranden ___ Reply to this item at: __

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #20, bug #66675 (group groff): [comment #19 comment #19:] > The patch to input.cpp in comment #14 fixes all my .char problems. ...as well as the font-file character-name problem of comment #6. Looks like this wraps things up! __

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #19, bug #66675 (group groff): The patch to input.cpp in comment #14 fixes all my .char problems. Thanks! ___ Reply to this item at:

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Follow-up Comment #21, bug #66675 (group groff): [comment #20 comment #20:] > [comment #19 comment #19:] >> The patch to input.cpp in comment #14 fixes all my .char problems. > > ...as well as the font-file character-name problem of comment #6. Looks like > this wraps things up! Excellent! Lo

[bug #57556] [troff] enforce left and right minimums as required by hyphenation patterns

Update of bug #57556 (group groff): Summary: Enforce left and right minimums as required by hyphenation patterns => [troff] enforce left and right minimums as required by hyphenation patterns ___ Follow-up Comment #11: [co

[bug #66675] [troff] valid .char definition starting with `\[u` provokes erroneous error

Update of bug #66675 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #22

[bug #66905] [PATCH] increase Unicode coverage by scaling back workaround for bug #63332

Update of bug #66905 (group groff): Summary: [PATCH] Increase Unicode coverage by scaling back workaround for bug #63332 => [PATCH] increase Unicode coverage by scaling back workaround for bug #63332 ___ Reply to this item

[bug #66905] [PATCH] Increase Unicode coverage by scaling back workaround for bug #63332

Update of bug #66905 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #3:

[bug #57556] Enforce left and right minimums as required by hyphenation patterns

Follow-up Comment #10, bug #57556 (group groff): [comment #6 comment #6:] > Design question: since a minimum hyphenation mode can be > computed based upon this characteristic of the pattern > files, should reading such a pattern file effectively set .hy? I want to revise my comment #7 answer to t

[bug #66931] [tbl] writes line number "1" wrongly in many `lf` requests since commit 25ef9f6bda

Update of bug #66931 (group groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #2:

[bug #57556] [troff] enforce left and right minimums as required by hyphenation patterns

Update of bug #57556 (group groff): Severity: 3 - Normal => 1 - Wish ___ Follow-up Comment #12: [comment #11 comment #11:] > I'll advise anyone just joining us of bug #55070 (already > mentioned a couple of tim