9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] htmlroff
Date: Thu,  5 Jan 2006 02:56:50 -0500	[thread overview]
Message-ID: <ee9e417a0601042356m54d7412bu65c79b22b11ab900@mail.gmail.com> (raw)
In-Reply-To: <7359f0490601042345p5a4e1abdj1bb77f81cd87aa2f@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.

I agree that modifying troff to add a driver wouldn't work,
because troff still thinks it is in charge of various layout
decisions and works at too low a level.  Troff2html fails
(when it does) for basically the same reasons.  Ms2html,
while originally intended to handle the -ms macros directly,
now has machinery in it to run arbitrary troff macros.  I think
that if this were fleshed out and a few primtives for HTML
added, then the HTML and -ms details could be moved
completely out into macro libraries.

> Don't you think a better long-term plan would be
> to abandon troff?

Yes.  But for what?

Russ


  reply	other threads:[~2006-01-05  7:56 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 [this message]
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=ee9e417a0601042356m54d7412bu65c79b22b11ab900@mail.gmail.com \
    --to=rsc@swtch.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).