> [...] I think the entire presentation-centric model within > which groff lives just about run its course. The future > belongs to structural markup and stylesheets, because of the > requirement for rendering in multiple output media including > the Web.
Point 1: I think we're talking about the typesetting engine itself. If someone wants to build a structural markup input on top of that, they're welcome. Point 2: It has to be programmable, otherwise it will never fill the niche of groff or TeX. If it's programmable, then the choice of presentational or structural markup is up to the user (resp. the macro programmer). Point 3: Personally, I use groff exclusively for printing out stuff (or creating PDFs as a sort of virtual paper) -- something to be read, as is, *by humans* -- nothing else. (For the web (if I must), I write HTML.) In principle, I could also print from the Browser, but the results are ghastly. I would not be willing to compromise typesetting quality in exchange for additional media I have no plans of using.
