[bug #65198] mom/examples/*.txt: change '-k' to '-K utf8'

Update of bug #65198 (group groff): Open/Closed:Open => Closed Planned Release:None => 1.24.0 ___ Follow-up Comment #7: commit

[bug #65198] mom/examples/*.txt: change '-k' to '-K utf8'

Update of bug #65198 (group groff): Status:None => Fixed ___ Follow-up Comment #6: [comment #4 comment #4:] > Comment #3 appears to misunderstand the point of comment #2: this

[bug #65198] mom/examples/*.txt: change '-k' to '-K utf8'

Update of bug #65198 (group groff): Status: Invalid => None Assigned to:gbranden => PTPi Open/Closed: Closed => Open Summary:

[bug #65198] mom/examples/*.txt: change '-k' to '-K utf8'

Follow-up Comment #5, bug #65198 (group groff): [comment #0 original submission:] > See "https://lists/gnu.org/archive/html/groff/2024-01/msg00106.html; This URL is malformed and should be https://lists.gnu.org/archive/html/groff/2024-01/msg00106.html (A followup, not linked from that URL, is

[bug #65099] 1.24.0 release goals

Follow-up Comment #4, bug #65099 (group groff): 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.

[bug #63354] Refine fallbacks.tmac

Follow-up Comment #36, bug #63354 (group groff): Maybe comment #34 and comment #35 are overthinking this. The requirement for U+2012 is that it occupy the same horizontal space as a figure. There is no requirement on the width of the mark itself. So what if the fallback simply uses the font's

[bug #63354] Refine fallbacks.tmac

Follow-up Comment #37, bug #63354 (group groff): (Of course, for fallback usage the .char in comment #35 and comment #36 should be .fchar.) ___ Reply to this item at: