From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] htmlroff
Date: Thu, 5 Jan 2006 09:43:41 +0100 [thread overview]
Message-ID: <8ccc8ba40601050043n24f6b8bbv29b8204cbee04e8e@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0601042356m54d7412bu65c79b22b11ab900@mail.gmail.com>
Regarding papers, I finally gave up troff and went back to latex.
Most places ask you to follow a given sty, and I got tired of
converting troff to latex (despite using a silly script for that).
Wouldn´t a converter from troff to latex be easier if we are talking
about generating html? latex is huge, but we already have it.
On 1/5/06, Russ Cox <rsc@swtch.com> wrote:
> > Don't you think a better long-term plan would be
> > to abandon troff?
>
> Yes. But for what?
>
> Russ
>
>
next prev parent reply other threads:[~2006-01-05 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 7:01 Russ Cox
2006-01-05 7:45 ` Rob Pike
2006-01-05 7:56 ` Russ Cox
2006-01-05 8:43 ` Francisco J Ballesteros [this message]
2006-01-05 8:48 ` Russ Cox
2006-01-05 8:59 ` Francisco J Ballesteros
2006-01-05 10:32 ` John Murdie
2006-01-05 18:48 ` Taj Khattra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ccc8ba40601050043n24f6b8bbv29b8204cbee04e8e@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).