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. >>> 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. kramdown is one of the best markup processor I had luck to try and its default markdown converts to man neatly. >> Ideally time-wise it would take the same time converting to one of them >> or add an add-on to kramdown to parse texinfo. > > Well, why using an importer for a generator when you can have the > input in the generator's native language? No, kramdown isn't just a markdown parser, it is a generic markup processor so in theory we could just feed it a texinfo grammar and have kramdown convert it in html and man. lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
