On Sat, Mar 23, 2024 at 07:13:38PM -0400, James Cloos wrote:
> Subject: Re: the Courier font family and nroff history
>
> So blame Jobs for Courier as the monospace family and for
> Times(12) as the serif family. And for Helvetica as the Sans
> family.
I think we need to remember the third party
At 2024-03-23T00:08:27+0100, Alejandro Colomar wrote:
> > Maybe I should do with grohtml what наб accused me of doing with
> > mdoc:
>
> Any links to that? Sounds like a funny discussion. :D
https://savannah.gnu.org/bugs/?65101
I admit that sometimes I enjoy disputation. This was not one of t
> "GB" == G Branden Robinson writes:
GR> I don't think Adobe standardized it
GR> for PostScript (and then PDF) for the _sole_ purpose of simulating
GR> terminal emulator, or even typewriter, output.
As I recall, it has frequently been posted over the years that the
selection of fonts which w
> [looping the groff list back in]
Again I got my wires crossed. Thanks.
> Do you happen to remember _when_ the CSRC got its 4014? About what
> year? Did Joe Ossanna have access to one early enough to use it in aid
> of troff development?
I think it was about the time of v6, well after the adv
At 2024-03-22T21:37:51-0700, Russ Allbery wrote:
> "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
> > di
[looping the groff list back in]
At 2024-03-23T11:37:51-0400, Douglas McIlroy wrote:
> > "BI" fonts can, it seems, largely be traced to the impact
> > of PostScript
>
> There was no room for BI on the C/A/T. It appeared in
> troff upon the taming of the Linotron 202, just after v7
> and five year
I've only half paid attention to this thread so if this has been mentioned,
sorry. I vaguely remember something like this:
.\" $ROFF -s -t $FILES
Near the top of the file and then there was a roff script that grepped out
that line, set ROFF to groff, FILE to $* and execed that sequence.
It's no
Dear Branden, Dave, Lennart and Peter (in alphabetical order),
thank you for your various replies and suggestions.
With regard to hidden caveats in my naive one-for-all attempt, I ignored
the potential consequences of the -s option. Thank you for pointing out
that.
So, next to introducing an -A
Hi Lennart,
I constantly ignore this trap due to my less-than-frequent postings.
Thank you for pointing out this one.
Best,
Oliver.
On 22/03/2024 22:26, Lennart Jablonka wrote:
Quoth Oliver Corff via:
Reply-to: Oliver Corff
This might not be the greatest of ideas. An MUA might just dec
I solved this problem for me by having a pseudo comment in the first line of my
documents
which indicates how this individual document is to be handled.
In my bash-script, that eventally calls groff with appropriate options and
preprocessors I have
FILE="$1"
# check for .\" eqn tbl add
10 matches
Mail list logo
