From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] htmlroff
Date: Wed, 4 Jan 2006 23:45:07 -0800 [thread overview]
Message-ID: <7359f0490601042345p5a4e1abdj1bb77f81cd87aa2f@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0601042301p39f1ab91ra54442288f8ba7c0@mail.gmail.com>
If I remember right - and I might not - I looked into an
html driver or terminal type for troff, but gave up and
did man2html instead, which took a radically smpler
tack than ms2html and scored a little better overall
but much worse in some cases.
Don't you think a better long-term plan would be
to abandon troff?
-rob
On 1/4/06, Russ Cox <rsc@swtch.com> wrote:
> Is anyone interested in hacking on a simple version
> of troff that generates html? The idea is to implement
> most of the troff base language and add primitives for
> putting in raw html and watching to make sure tags get
> matched properly. It's considerably simpler than troff
> since one doesn't have to deal with the low-level details
> of text layout, character widths, and so on.
>
> The idea is that then htmlroff could use the existing
> macro packages more or less directly, perhaps with a
> few small changes. It would replace both ms2html,
> which works at a higher level, and troff2html, which
> works at a lower level. It could format the manual
> pages as well as the papers, and the resulting html
> would actually look good and be easy to change
> (just edit the macros).
>
> Completing the picture would be versions of pic, eqn,
> and tbl that emit SVG, MathML, and HTML tables.
>
> I've started to cannibalize ms2html to build htmlroff,
> but I really don't have much time to spend on it.
>
> Russ
>
next prev parent reply other threads:[~2006-01-05 7:45 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 [this message]
2006-01-05 7:56 ` Russ Cox
2006-01-05 8:43 ` Francisco J Ballesteros
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=7359f0490601042345p5a4e1abdj1bb77f81cd87aa2f@mail.gmail.com \
--to=robpike@gmail.com \
--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).