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.
According to its Debian in http://lists.debian.org/[email protected], transitioning from texi2html to makeinfo is supposed to be easy. Unfortunately, this does not seem to be the case for Libav, and I'm still trying to figure out why. Please correct if I'm wrong, but AFAIUI, we use the texinfo source not only to generate html, but also manpages using an included texi2pod.pl script. At this point I have to ask, I understand the desire to have a single source from which we generate both manpages and html pages. However, since we do not generate info pages, why using texinfo in the first place? Wouldn't it be easier for everyone if we used POD directly, maintain that, and use POD as source for generating the HTML pages? I understand that it is effort to make pod2html produce HTML page that follow the Libav look. However, the same applies to makeinfo, since the output tuning and initialization files for texi2html no longer applies to makeinfo and has to be redone anyways. What else keeps up with texinfo? -- regards, Reinhard _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
