[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: <OK> Re: [Groff] Re: Simplifying groff documentation
From: |
Eric S. Raymond |
Subject: |
Re: <OK> Re: [Groff] Re: Simplifying groff documentation |
Date: |
Sun, 24 Dec 2006 14:39:45 -0500 |
User-agent: |
Mutt/1.4.2.2i |
M Bianchi <address@hidden>:
> Since DocBook deduces _meaning_ from the presentation markup
DocBook does nothing of the sort. It's doclifter that does that.
> then I will claim
> that the correct path needs to be something like ...
> groff -man -> DocBook +-> HTML
> |
> +-> groff -man_extended
>
> where new meaning markup is inserted back into the source document form
> (assuming that foo.man_extended becomes the prefered edited file).
I think there would be very little point in this.
groff markup is presentation-level. It's good at that. If you try to
turn it into a structural markup, I predict you will get exactly the
results Bernd Warken already has -- you'll break non-groff viewers
without producing anything that's adequate as a structural
description.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
- Re: [Groff] Re: Simplifying groff documentation, Larry Kollar, 2006/12/23
- [Groff] Re: Simplifying groff documentation, Gunnar Ritter, 2006/12/25
- [Groff] Re: Simplifying groff documentation, Eric S. Raymond, 2006/12/25
- Re: [Groff] Re: Simplifying groff documentation, Gunnar Ritter, 2006/12/25
- Re: [Groff] Re: Simplifying groff documentation, Eric S. Raymond, 2006/12/25
- Re: [Groff] Re: Simplifying groff documentation, Gunnar Ritter, 2006/12/26
- Re: [Groff] Re: Simplifying groff documentation, Eric S. Raymond, 2006/12/26
- Re: [Groff] Re: Simplifying groff documentation, Gunnar Ritter, 2006/12/26
- Re: [Groff] Re: Simplifying groff documentation, Eric S. Raymond, 2006/12/26
- Re: [Groff] Re: Simplifying groff documentation, Gunnar Ritter, 2006/12/26