Re: the Courier font family and nroff history

"G. Branden Robinson" writes: > Okay...by this time groff had for about 10 years been producing > device-independent _terminal_ output from troff(1). On the other, that > is its own peculiar little language. Maybe the author just didn't want > to deal with *roff, or didn't want to count on GNU

Re: the Courier font family and nroff history

At 2024-03-22T22:12:08-0500, G. Branden Robinson wrote: > (Kernighan didn't completely unify terminals under the > device-independent troff scheme presented in CSTR #54 CSTR #97 > --nevertheless its "driving tables" for terminal devices bore a > startling resemblance to "DESC" files for

Re: the Courier font family and nroff history

At 2024-03-22T17:06:40-0700, Russ Allbery wrote: > "G. Branden Robinson" writes: > > > That's a good argument against grotty(1) emitting overstriking > > sequences, at least by default, and yet that the people swiftest to > > anger on this subject argue _for_ it. > > I'm not fully following

Re: the Courier font family and nroff history

On Fri, Mar 22, 2024 at 7:07 PM Russ Allbery wrote: > > The stated reason was that the output was device-independent, unlike > output that embeds formatting codes derived from device-specific termcap > entries, and they really liked the bold and underlining rather than the > plain text or *ad

Re: the Courier font family and nroff history

"G. Branden Robinson" writes: > That's a good argument against grotty(1) emitting overstriking > sequences, at least by default, and yet that the people swiftest to > anger on this subject argue _for_ it. I'm not fully following this argument, but (assuming I've not completely lost the train of

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 05:45:14PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-22T21:24:10+0100, Alejandro Colomar wrote: > > Heh, we're comparing different things. I'm comparing `eqn -Tps` to > > nothing at all, while you're comparing `eqn -Tps` to `eqn -Thtml`. If

Re: Running the grohtml pipeline as a pipeline

Hi Alex, At 2024-03-22T21:24:10+0100, Alejandro Colomar wrote: > Heh, we're comparing different things. I'm comparing `eqn -Tps` to > nothing at all, while you're comparing `eqn -Tps` to `eqn -Thtml`. If > I diff the same things you're diffing, then I see the same as you. Ahh. Okay. Yes, I

Re: An extremely lazy proposal

Hi Oliver, At 2024-03-22T21:01:27+0100, Oliver Corff via wrote: > recently I compiled, and re-compiled, and again recompiled a set of > various documents with different tables, equations etc.. For each of > the documents, the precise requirements of preprocessors were > different, and more often

Re: An extremely lazy proposal

I don't have any complaint with your proposal, but it sounds like what you need is a makefile or script to insure groff runs are done the same way every time. More simplistically, you can define a shell alias to invoke all preprocessors: "alias groff='groff -k -e -p -t -R'". (Or name the alias

Re: An extremely lazy proposal

On Fri, Mar 22, 2024, Oliver Corff via wrote: > Dear All, > > recently I compiled, and re-compiled, and again recompiled a set of > various documents with different tables, equations etc.. For each of the > documents, the precise requirements of preprocessors were different, and > more often than

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

On Friday, 22 March 2024 16:59:14 GMT Alejandro Colomar wrote: > ow, how am I supposed to > get that patch without anyone tampering it during its trip to my > computer? :( derij@ws:~$ md5sum /var/www/chinese.patch.gz 109e2681b7402ca55118226aa575b6d3 /var/www/chinese.patch.gz

Re: An extremely lazy proposal

Quoth Oliver Corff via: Reply-to: Oliver Corff This might not be the greatest of ideas. An MUA might just decide to reply to you only, instead of to you and the list. Dear All, recently I compiled, and re-compiled, and again recompiled a set of various documents with different tables,

Re: the Courier font family and nroff history (was: mandoc(1)'s man pages, groffed, and Project KIC)

Quoth G. Branden Robinson: At 2024-03-19T19:59:58+, Lennart Jablonka wrote: Right. We can emulate the nonsense typewriter /emulators/ do. I do think that we shouldn’t do that, either. I would not describe character-cell video terminals as "typewriter emulators" precisely because they

Re: Running the grohtml pipeline as a pipeline

On Fri, Mar 22, 2024 at 03:15:11PM -0500, G. Branden Robinson wrote: > At 2024-03-22T20:56:28+0100, Alejandro Colomar wrote: > > I'm quite surprised that you aren't even getting the warning due to > > `eqn -Thtml`. > > I did. I elided it. I also elided nearly all of my garrulous shell > prompt.

Re: Running the grohtml pipeline as a pipeline

At 2024-03-22T20:56:28+0100, Alejandro Colomar wrote: > I'm quite surprised that you aren't even getting the warning due to > `eqn -Thtml`. I did. I elided it. I also elided nearly all of my garrulous shell prompt. ;-) > I was running > > $ troff --version > GNU troff (groff)

An extremely lazy proposal

Dear All, recently I compiled, and re-compiled, and again recompiled a set of various documents with different tables, equations etc.. For each of the documents, the precise requirements of preprocessors were different, and more often than not, I forgot to set the appropriate groff option when

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 02:44:26PM -0500, G. Branden Robinson wrote: > At 2024-03-22T20:10:51+0100, Alejandro Colomar wrote: > > It reduces the base paragraph inset (did I use the right term? :) to > > almost nothing. > > I have to say I regard this as a pretty minor problem compared

Re: Running the grohtml pipeline as a pipeline

Hi Alex, At 2024-03-22T20:10:51+0100, Alejandro Colomar wrote: > Whoops! I passed two different file names at different stages. I > obviously wanted to say this: > > $ preconv man3/_Generic.3 \ > | tbl \ > | troff -man -Thtml -wbreak \ > |

Re: Running the grohtml pipeline as a pipeline

Hi Branden, On Fri, Mar 22, 2024 at 01:53:51PM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-18T12:38:30+0100, Alejandro Colomar wrote: > > I'm considering using grohtml(1) in the Linux man-pages, to replace > > man2html(1), which crashes on tzfile(5) --which has correct man(7)--.

Re: the Courier font family and nroff history (was: mandoc(1)'s man pages, groffed, and Project KIC)

[self-correction] At 2024-03-22T13:24:04-0500, G. Branden Robinson wrote: > and video terminals emulated typewriters well enough for unserious > work like formatting man pages on a screen. Err, this is pretty hugely false. They didn't. That's why you had to pipe nroff's output through col(1)

Re: Running the grohtml pipeline as a pipeline

Hi Alex, At 2024-03-18T12:38:30+0100, Alejandro Colomar wrote: > I'm considering using grohtml(1) in the Linux man-pages, to replace > man2html(1), which crashes on tzfile(5) --which has correct man(7)--. Well, all right. Demand may drive improvement to grohtml more reliably than abandonment

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

On Fri, Mar 22, 2024 at 05:56:58PM +, Deri wrote: > On Friday, 22 March 2024 16:59:14 GMT Alejandro Colomar wrote: > > ow, how am I supposed to > > get that patch without anyone tampering it during its trip to my > > computer? :( > > derij@ws:~$ md5sum /var/www/chinese.patch.gz >

the Courier font family and nroff history (was: mandoc(1)'s man pages, groffed, and Project KIC)

At 2024-03-19T18:28:13+, Lennart Jablonka wrote: > Quoth G. Branden Robinson: > > > And the page numbers reset at the start of each section. Which > > > they shouldn’t do—the book is one unit; it should get its own page > > > numbers. And in other books, you don’t usually see page numbers >

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

Hi Branden! On Fri, Mar 22, 2024 at 11:30:11AM -0500, G. Branden Robinson wrote: > Hi Alex, > > At 2024-03-17T23:44:07+0100, Alejandro Colomar wrote: > > On Sun, Mar 17, 2024 at 05:23:20PM -0500, G. Branden Robinson wrote: > > > Following up my earlier announcement regarding man(7),[1], I'm > >

Re: Milestone reached: hyperlinked mdoc(7) documents in PDF

Hi Alex, At 2024-03-17T23:44:07+0100, Alejandro Colomar wrote: > On Sun, Mar 17, 2024 at 05:23:20PM -0500, G. Branden Robinson wrote: > > Following up my earlier announcement regarding man(7),[1], I'm > > pleased to report that we have a functioning PDF hyperlink story for > > the mdoc package.

[bug #60034] [mdoc] `Mt` macro should validate its arguments

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

[bug #64004] [troff] make character and glyph handling more discoverable (.pchar, ".if C", ".if G")

Update of bug #64004 (group groff): Summary: make character and glyph handling more discoverable (.pchar, ".if C", ".if G") => [troff] make character and glyph handling more discoverable (.pchar, ".if C", ".if G") ___

[bug #52463] anything that talks to standard error should identify itself

Update of bug #52463 (group groff): Dependency Removed: => bugs #57611 ___ Reply to this item at: ___ Message