[bug #62826] [PATCH] [tmac] options "-mandoc" and '-C' are not compatible

Follow-up Comment #1, bug #62826 (project groff): There were extra two lines ". fi" in the first patch. >From 24e4cf7dfedd58b2a1be6c600d27fed937d24fb0 Mon Sep 17 00:00:00 2001 From: Bjarni Ingi Gislason Date: Thu, 28 Jul 2022 12:32:11 + Subject: [PATCH] [tmac] options "-mandoc" and '-C'

[bug #62830] [grops] support CJK fonts encoded in UTF16

URL: Summary: [grops] support CJK fonts encoded in UTF16 Project: GNU troff Submitter: takuji Submitted: Thu 28 Jul 2022 12:56:27 PM UTC Category: Device grops S

[bug #62830] [grops] support CJK fonts encoded in UTF16

Additional Item Attachment, bug #62830 (project groff): File name: cjk-ps.patch Size:32 KB ___ Reply to this item at:

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #4, bug #62825 (project groff): [comment #3 comment #3:] > So it seems that groff does a single pass through each page from > top to bottom: start a new page, then print the header, then > print the body, then print any footnotes, then lastly print the > footer. It then starts th

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #5, bug #62825 (project groff): [comment #4 comment #4:] > Consider a page where the top half wraps up section 1.4, then section 2.1 begins, and has a paragraph or two on the lower half of the page. Here you want your page header to indicate section 1.4, since that's the section

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #6, bug #62825 (project groff): [comment #5 comment #5:] > Hmm, every book I've ever seen with section numbers/titles in > the header uses the info for the last section on the page. You are right; I spoke from ignorance. I opened an O'Reilly book at random, and it does indeed p

[bug #62825] Incorrect section number using \*($n in a header

Update of bug #62825 (project groff): Category:Macro me => Macro - others/general ___ Follow-up Comment #7: [comment #6 comment #6:] > [comment #5 comment #5:] > > Hmm, every book I've ever seen with secti

[bug #62825] Incorrect section number using \*($n in a header

Follow-up Comment #8, bug #62825 (project groff): Whoops, I didn't finish editing my reply. [comment #7 comment #7:] > I reckon what we can do is leave the existing header trap macro names in place, but change them to just mark the vertical location with `mk`. The footer trap can set its own ma

[bug #62825] page header info should correspond to last section on the page

Update of bug #62825 (project groff): Summary: Incorrect section number using \*($n in a header => page header info should correspond to last section on the page ___ Reply to this item at:

[bug #62833] [PATCH] tty.cpp: prefer showing data over opinion

URL: Summary: [PATCH] tty.cpp: prefer showing data over opinion Project: GNU troff Submitter: bjarniig Submitted: Fri 29 Jul 2022 01:16:21 AM UTC Category: Device - others/gener

[bug #62825] page header info should correspond to last section on the page

Follow-up Comment #9, bug #62825 (project groff): [comment #7 comment #7:] > One of these was the same as in the pile of books I cited > recently to undermine Ingo's claim that the overwhelming > majority of publishers in all fields set headers as mandoc(1) > does. (Off topic for this bug, but I

[bug #62265] [tbl] tables in nroff mode seem to want one too many vees

Follow-up Comment #3, bug #62265 (project groff): The detailed analysis in http://lists.gnu.org/r/groff/2022-07/msg00223.html suggests that this and bug #62471 are respectively the vertical and horizontal manifestations of the same bug. ___

[bug #62471] [tbl] draws horizontal lines that are too long by 1n in nroff mode

Follow-up Comment #4, bug #62471 (project groff): The detailed analysis in http://lists.gnu.org/r/groff/2022-07/msg00223.html suggests that this and bug #62265 are respectively the horizontal and vertical manifestations of the same bug. ___

[bug #62830] [grops] support CJK fonts encoded in UTF16

Update of bug #62830 (project groff): Severity: 3 - Normal => 1 - Wish ___ Follow-up Comment #1: (removed a duplicate attachment) ___ Re