> > even though massive amount of *manpower* has been put in this
I'm calling you out on that pun. =) Regarding HTML... I fully hear what you're saying. Somebody asked for a realtime preview of manual-page editing <https://github.com/Alhadis/language-roff/issues/3> for Atom (a text editor which is built using web technologies: HTML, CSS, JavaScript, etc). I thought it'd be simple to implement in barebones HTML, but quickly realised what I was getting myself into. So I've decided to use HTML5 <canvas> instead, piping Groff's intermediate output through a separate process and lexing the instructions to plot basic drawing operations in a side pane. Heck of a lot simpler than translating HTML to/from *Roff... =) On 20 November 2016 at 02:13, Steffen Nurpmeso <stef...@sdaoden.eu> wrote: > <hoh...@arcor.de> wrote: > |Werner LEMBERG <w...@gnu.org> wrote (Thu, 17 Nov 2016 09:02:52 +0100 > |(CET)): > ... > |> Alas, Vienna is a bit too far away from Berlin... BTW, what do you > |> mean with `left behind'? > ... > |Also: > |markdown/ ReST -> HTML is superior to groff -> HTML. > > Surely this is not necessarily true. I would love to have a HTML > filter that just works, in order to simply convert Unix manual > pages to HTML if i want to. (And, yes, with mdocmx anchors and > thus fully interlinked.) Unfortunately it is not that easy even > though massive amount of manpower has been put in this, but if > i convert the manual of the MUA i am sticking in so much that > i seem to have disappeared i need two of my work days of manual > adjustments to get it done, so, and only because of this, i agree. > Otherwise i would not. Oh yes, there is plenty of interest. > > --steffen > >
