Re: The 3-faces problem

The PostScript from groff -man (version 1.22.4) applied to > .RB [ U ] INT \fIN\fP _WIDTH is /F0 10/Times-Roman@0 SF 433.3(a\(b\) a\(b\))72 48 R([)108 84 Q/F1 10 /Times-Bold@0 SF(U)A F0(])A F1(INT)A/F2 10/Times-Italic@0 SF(N)A F1 (_WIDTH)A F0 226.78(c1)303.78 768 S 0 Cg EP This defines /F0 as r

Re: The 3-faces problem

Hi, Branded! On 11/2/21 19:45, G. Branden Robinson wrote: Hi, Alex! At 2021-11-02T19:07:05+0100, Alejandro Colomar (man-pages) wrote: On 11/2/21 18:49, G. Branden Robinson wrote: printf '_\\fB_\\fI_\\f(BI_\n' | nroff | cat -s Yes, I see 4 different glyphs. Okay, so that much is sane in ou

Re: an officially maintained version of dformat outthere ?

hello Ralph, > One small help may be > mutool draw -o paper.txt pdfRiXK_KnNhU.pdf > which doesn't do too bad a job of extracting the code. There's no > indentation, ASCII circumflexes will need resurrecting from their > flashier cousin, etc. Thank you so much: it was good enough so i can get

Re: pic doesn't center when i use a macro

hello Douglas, > Remember that macros work by substitution. So each line of label_for > becomes a separate line in the macro-expanded program. A label alone > on a line gets plotted at the current point, which in this case is > last box.e. That, with the explainations from Tadziu, helped a lot. T

Re: The 3-faces problem

Hi, Alex! At 2021-11-02T19:07:05+0100, Alejandro Colomar (man-pages) wrote: > On 11/2/21 18:49, G. Branden Robinson wrote: > > printf '_\\fB_\\fI_\\f(BI_\n' | nroff | cat -s > > Yes, I see 4 different glyphs. Okay, so that much is sane in our respective environments. :) > I was using xface ter

[bug #61417] [tbl] core dump when further spanning a first-row (invalid) downward span

URL: Summary: [tbl] core dump when further spanning a first-row (invalid) downward span Project: GNU troff Submitted by: gbranden Submitted on: Tue 02 Nov 2021 06:08:08 PM UTC Categor

Re: The 3-faces problem

On 11/2/21 18:49, G. Branden Robinson wrote: Hi, Alex! At 2021-11-02T17:57:28+0100, Alejandro Colomar (man-pages) wrote: Hey Branden! I need your wisdom :) I hope to find some, someday... ;-) I'm facing the 3-faces problem right now. I'm trying to write the following sentence: [ The macro

Re: The 3-faces problem

Hi Tadziu, On 11/2/21 18:51, Tadziu Hoffmann wrote: - It's all a single identifier, so breaking it into multiple lines to avoid using \f would hurt readability. I think it's a matter of debate whether .RB [ U ] INT \fIN\fP _WIDTH or .RB [ U ] INT\c .IB N _WIDTH is more readable.

Re: The 3-faces problem

> - It's all a single identifier, so breaking it into multiple > lines to avoid using \f would hurt readability. I think it's a matter of debate whether .RB [ U ] INT \fIN\fP _WIDTH or .RB [ U ] INT\c .IB N _WIDTH is more readable. In the latter at least it's obvious in which typeface

Re: The 3-faces problem

Hi, Alex! At 2021-11-02T17:57:28+0100, Alejandro Colomar (man-pages) wrote: > Hey Branden! > > I need your wisdom :) I hope to find some, someday... ;-) > I'm facing the 3-faces problem right now. > I'm trying to write the following sentence: > > [ > The macros [U]INTN_WIDTH expand to the widt

The 3-faces problem

Hey Branden! I need your wisdom :) I'm facing the 3-faces problem right now. I'm trying to write the following sentence: [ The macros [U]INTN_WIDTH expand to the width in bits of these types (N). ] With the following requisites: - N is variable, and so (I think) I want it in italics. - INT _W

Re: Git, where zombie branches shamble again

On Tue, Nov 02, 2021 at 07:20:03AM +, Werner LEMBERG wrote: > > >> You absolutely _did_ rewrite history ... not just once, but twice! > >> You deleted an _entire branch_ of published development history, > >> then after my subsequent push had reinstated it, you deleted it > >> once again! If

Re: an officially maintained version of dformat outthere ?

Hi Marc, > * the patched version of the script is in the pdf file and > a simple copy/paste just ruins the code. One small help may be mutool draw -o paper.txt pdfRiXK_KnNhU.pdf which doesn't do too bad a job of extracting the code. There's no indentation, ASCII circumflexes will need re

Re: Git, where zombie branches shamble again

>> You absolutely _did_ rewrite history ... not just once, but twice! >> You deleted an _entire branch_ of published development history, >> then after my subsequent push had reinstated it, you deleted it >> once again! If that isn't rewriting history, then I'd like to know >> what you would call

gsview ghostscript

If somebody still uses gsview for watching postscript files. I made a patch to install gsview with the latest ghostscript 9.55 Maybe it is a little bit offtopic but I figured since groff is still a lot of postscript some of you might be interested. The patch can be found on gemini: gemini://yasend