On Dec 7, 2013 4:17 PM, "Luca Barbato" <[email protected]> wrote: > > On 07/12/13 19:10, Reinhard Tartler wrote: > > On Sat, Dec 7, 2013 at 1:00 PM, Luca Barbato <[email protected]> wrote: > >> On 07/12/13 16:31, Reinhard Tartler wrote: > >>> Hi, > >>> > >>> it seems that a critical tool in our documentation infrastructure has > >>> become deprecated upstream for some years now: texi2html. It seems > >>> that it has become obsolete due to makeinfo has grown proper html > >>> generating capabilities on its own. > >> > >> It is partially lacking in generation but nothing that can't be hacked > >> around. > > > > You you mean that customizing makeinfo's HTML output to look "good > > enough" is feasible? I'm not familiar enough with our requirements > > here to judge on that, so I'm curious. > > "fixing" the new perl abomination to do our bidding isn't impossible if > the upstream collaborates.
Off topic, TexInfo is a great language with crappy tools. > > >>> What else keeps up with texinfo? > >> > >> The fact it is easy to use, has not many dependencies (perl) and it is > >> exactly to the point feature-wise, asciidoc and kramdown could fit the > >> bill but that would require conversion effort. > > > > TBH, I'd prefer asciidoc (python) over kramdown (ruby), but that maybe > > just me. I've only touched asciidoc briefly so far, and managed to get > > somewhat useful results. I haven't used kramdown at all so far. > > markdown is simpler than asciidoc and doesn't require a trip to xml to > get good output. I agree. MD is so simple to use and it's also wider-spread (in part because of GiHub). But kramdown doesn't support man output. Also pandoc is pretty nice too, but it is written in Haskell... Haven't tried asciidoc though. Timothy _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
