On Mon, Nov 23, 2009 at 12:00:02AM +0100, Thomas Keller wrote: > For example, yes. I have basically two wishes: > > a) Keep the (nested) structure of a document intact, so no "hacks" > (sorry) like breaking up <pre> tags because they're nested
I won't do that. I want the html produced to be valid. But it should be quite easy to do an init file where <pre> are opened and closed when complex formats are opened and closed, and do nothing for 'preformatted' elements. The structure is not lost since the complex formats nesting is kept, though the 'preformatted' are always leafs (like paragraphs, in fact except that they are only closed by other block formats opening and not by empty lines). > b) Keep the HTML 100% stylable, so no "artificial" whitespaces which one > cannot influence / remove via CSS. I try to do that as much as possible, but I am not a CSS expert, so I don't know what can be done with CSS. Here is a list of formatting that cannot be handled through CSS: * @file, @indicateurl have quotes that are not influenced by CSS. * @key is within < > * @menu have a complicated table structure. * @printindex has also a complicated table structure. * @cartouche is also implemented with a simple table Also some formatting results may lack a class attribute. If you want more class attributes for specific formatting results, just say so. > You're now speaking of texi2html, not makeinfo, right? Any chance that > makeinfo's HTML output is updated as well? I'm just asking because we're > currently not using texi2html and this might be a new build dependency > for our project then... Normally texi2html implementation should be used as makeinfo soon, (makeinfo will be texi2html with different defaults that match better makeinfo in C defaults). -- Pat
