[bug #61434] [man] want support for hyperlinked paragraph tags

Follow-up Comment #3, bug#61434 (group groff): This was an important follow-up commit. commit 52a5a89c0da9f90c83441b8eb8020344a8468686 Author: G. Branden Robinson Date: Thu Feb 1 23:23:45 2024 -0600 [man]: Back away from color management concerns. Hyperlink colors in PDF were sh

[bug #65215] [man] .MT/.ME and .UR/.UE should make hyperlinks in PDF

Update of bug#65215 (group groff): Planned Release:None => 1.24.0 ___ Reply to this item at: ___ Message s

[bug #57515] [troff] "-Wdeprecated-copy" warning in node.cpp

Update of bug#57515 (group groff): Severity: 3 - Normal => 2 - Minor Item Group: Build/Installation => Lint ___ Reply to this item at:

[bug #64597] [mom] spurious newline after image label

Follow-up Comment #10, bug#64597 (group groff): commit 11016d37f1e16fa71407f9802b105c016263128c Author: Peter Schaffter Date: Sat Aug 26 14:25:38 2023 -0400 [mom]: Fixes captions not attaching to PDF_IMAGE labels. ___ Reply to t

[bug #61434] [man] want support for hyperlinked paragraph tags

Follow-up Comment #4, bug#61434 (group groff): [comment #3 comment #3:] > This was an important follow-up commit. > commit 52a5a89c0da9f90c83441b8eb8020344a8468686 > Author: G. Branden Robinson > Date: Thu Feb 1 23:23:45 2024 -0600 > ... > Unfortunately, "pdf.tmac" doesn't > expose a

[bug #61434] [man] want support for hyperlinked paragraph tags

Follow-up Comment #5, bug#61434 (group groff): Hi Deri, [comment #4 comment #4:] > [comment #3 comment #3:] > > This was an important follow-up commit. > > commit 52a5a89c0da9f90c83441b8eb8020344a8468686 > > Author: G. Branden Robinson > > Date: Thu Feb 1 23:23:45 2024 -0600 > > > ... > >

[bug #65241] [mm] support bold-italic

URL: Summary: [mm] support bold-italic Group: GNU roff Submitter: None Submitted: Fri 02 Feb 2024 11:11:40 PM UTC Category: Macro mm Severity: 3 - Normal

[bug #62921] want another monospaced font in the default set

Update of bug#62921 (group groff): Status: Need Info => None ___ Follow-up Comment #6: This bug was put into Need Info status with comment #1, which asked for feedback that the submitter s

[bug #65241] [mm] support bold-italic

Update of bug#65241 (group groff): Severity: 3 - Normal => 1 - Wish ___ Follow-up Comment #1: [comment #0 original submission:] > Buried in the novella that is bug #62921 is this observation: >

[bug #62921] want another monospaced font in the default set

Follow-up Comment #7, bug#62921 (group groff): [comment #1 comment #1:] > groff's _ms_ and _me_ have support for bold-italic already (and have > for decades), and it wouldn't be hard to add it to our _mm_ either; This has been filed as bug #65241. [comment #5 comment #5:] > Ideally, distributors

[bug #62921] want another monospaced font in the default set

Follow-up Comment #8, bug#62921 (group groff): [comment #7 comment #7:] > [comment #1 comment #1:] > > groff's _ms_ and _me_ have support for bold-italic already (and have > > for decades), and it wouldn't be hard to add it to our _mm_ either; > > This has been filed as bug #65241. Thanks (to wh

[bug #65242] [gropdf] should validate and diagnose ill-formed "download" files

URL: Summary: [gropdf] should validate and diagnose ill-formed "download" files Group: GNU roff Submitter: gbranden Submitted: Sat 03 Feb 2024 12:32:11 AM UTC Category: Driver

[bug #65190] [man, mdoc] revise implementation of continuous rendering mode

Follow-up Comment #8, bug#65190 (group groff): [comment #6 comment #6:] > I've heard no demand expressed for continuously rendered > ms/me/mm/mom documents. Less self-serving instances: * http://lists.gnu.org/r/groff/2006-05/msg00102.html * http://lists.gnu.org/r/groff/2008-03/msg00012.html * htt

[bug #62921] want another monospaced font in the default set

Follow-up Comment #9, bug#62921 (group groff): [comment #8 comment #8:] > Thanks (to whoever that anonymous submitter was ;-) )! You've probably deduced this, but the reason I sometimes file groff bugs "anonymously" is not to evade credit/blame, but so that I'm not forever tied to a bug I have no

[bug #60930] Integrate Peter Schaffter's font installer script into groff

Follow-up Comment #6, bug#60930 (group groff): [comment #0 original submission:] > * Make the script portable by removing dependencies on > bash-specific features I'm now wondering if there's some wisdom to doing a first cut that simply checks whether bash is available and bails gracefully if not

[bug #60930] Integrate Peter Schaffter's font installer script into groff

Follow-up Comment #7, bug#60930 (group groff): Branden mentioned two more to-do items in the email cited in comment #5: * giving it a less name-space-stomperific name ("groff-font-install" or "groff-install-font" would be clear enough, but I think either would annoy me [and other users] when tab-c