[bug #62923] Broken aliases in PDF font description file

Follow-up Comment #2, bug #62923 (project groff): Thank you for fixing it! I applied the fix you provided and it works but I noticed that one thing is still broken: if you add an alias with name radicalex to sqrtex in XITSMR, the radicalex is rendered on the same position as sqrt (in groff_out the

[bug #62801] [me] doc/meref.me.in: Clarify a couple points about empty macro arguments

Update of bug #62801 (project groff): Status:None => Confirmed ___ Follow-up Comment #2: [comment #0 original submission:] > A few -me macros (.ip, .sh, .$p, .2c since commit 01cf10eb

[bug #62926] [mdoc] align styling of headers and man page cross references with man(7)

URL: Summary: [mdoc] align styling of headers and man page cross references with man(7) Project: GNU troff Submitter: gbranden Submitted: Sat 20 Aug 2022 01:02:24 PM UTC Categor

[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly

Update of bug #62923 (project groff): Category: General => Device gropdf Item Group:None => Incorrect behaviour Status: Fixed => In Progress Summary: Bro

[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly

Follow-up Comment #4, bug #62923 (project groff): Would the submitter care to identify themselves? I like to credit helpful reporters in the ChangeLog, and it's not every day we get a ticket submitter who understands the _troff_ output format. ___

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

Update of bug #62921 (project groff): Severity: 3 - Normal => 1 - Wish Summary: [Request] Add another monospaced font to the default fonts => want another monospaced font in the default set _

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

Update of bug #62921 (project groff): Status:None => Need Info ___ Follow-up Comment #1: [comment #0 original submission:] > By default groff comes with 6 proportional fonts (Avant Garde,

[bug #62926] [mdoc] align styling of headers and man page cross references with man(7)

Follow-up Comment #1, bug #62926 (project groff): No comment on the first sentence because it is not very specific. I do not object to the rest of the original submission. But i strongly disagree with the summary. mdoc(7) has always consistently styled .Xr as \fR for terminal output whereas man

[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly

Follow-up Comment #5, bug #62923 (project groff): I've just created an account. The output is really easy to understand (thanks to groff_out(5))! [comment #4 comment #4:] > Would the submitter care to identify themselves? I like to credit helpful reporters in the ChangeLog, and it's not every da

[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly

Follow-up Comment #6, bug #62923 (project groff): [comment #5 comment #5:] > I've just created an account. The output is really easy to understand (thanks to groff_out(5))! Hello and welcome! I'm glad to hear that about _groff_out_(5); that is a man page that I have not rewritten yet, though I

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

Follow-up Comment #2, bug #62921 (project groff): I concur that this (an nice monospaced font) would be desirable. begin-off-topic: PTMono is a _very_ nice free monspaced font. extremely readable on screen. use it as my standard font in the terminal. PTSerif and PTsans are also very decent (and I

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

Follow-up Comment #3, bug #62921 (project groff): Hi Joerg, [comment #2 comment #2:] > I concur that this (an nice monospaced font) would be desirable. > > begin-off-topic: PTMono is a _very_ nice free monspaced font. extremely readable on screen. use it as my standard font in the terminal. PTSe

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

Follow-up Comment #4, bug #62921 (project groff): [comment #1 comment #1:] > The main practical problem here is that while we could certainly generate _groff_ font descriptions file for some or all of those, and ship them, users _still_ won't get those fonts in the output they generate unless the

[bug #62923] [gropdf] glyph aliases in in font description files not parsed correctly

Follow-up Comment #7, bug #62923 (project groff): This probably deserves its own bug number, since the original problem is now fixed. This second reported issue is not specific to PDF output, the same problem exists with postscript, which is indicative the issue is other than the output driver, o

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

Follow-up Comment #5, bug #62921 (project groff): [comment #4 comment #4:] > Hi, original submitter here. Yes, your solution would be fine, but I'm a bit confused. For groff 1.22.4 in Fedora 36 I noticed there are 3 *.pfa_ files in /usr/share/groff/1.22.4/font/devps/: freeeuro.pfa_, symbolsl.pfa_

[bug #24527] [grohtml] equations in .tl misplaced

Update of bug #24527 (project groff): Summary: equations in .tl confuses grohtml => [grohtml] equations in .tl misplaced ___ Reply to this item at: ___