We used to have a situation where we would have a .html project file and it would automatically substitute a .xhtml file for browsers that support mathml. Then we started using MathJax, and giving the .xhtml to all browsers. Then there were some changes in LaTeXML that started producing XHTML that's not compatible with the HTML5 that we're using, so now we have support for .html (HTML 4), .xhtml (XHTML 1.0), and .html5 (HTML 5), but we're only using .html5 except on wiki pages that explicitly invoke one of the others. I think we now have .html files automatically upgrade to .html5 in compatible browsers.
But we have a lot of pages at this point that use .xhtml files explicitly, because that's been the only way to make a .tex file programmatically and display it as html. It garbles the wiki page's layout until it's changed manually from .xhtml to .html5.
This is a mess. It should be fixed. People should be able to just deal with .html files and expect good behavior.
Anonymous
I just did a little test, and .html does not get automatically upgraded to .html5. If it did, we would probably be able to just say .html and expect forward compatibility and correct MathML output.
For pdf files, we have a %.pdf pattern that gives you the same file as %.latex.pdf. It would be great to provide %.html as a synonym for %.latexml.html5.
OK, well, %.html is pretty easy to provide, I guess. I've added it to the makefile and it seems to work, but should be tested a bit for how it handles math, fallback to/from xhtml, etc, or whatever.
Also I guess there's a design question about whether people want the simple filename %.html to be understood as a partial HTML file for insertion into a larger page (what I just put into the makefile) or a full HTML page (%.standalone.html).
Done. %.latexml.html now does the same thing as %.latexml.html5. As a consequence, there's no longer a rule for making LaTeXML HTML output with png images instead of MathML.
Additionally, %.html when there's a corresponding %.tex does the same thing as %.latexml.html. It shouldn't interfere with %.html rules for other kinds of sources, as long as there isn't a .tex file with the same basename involved.
Note, though, that while %.html makes the same output as %.latexml.html, it doesn't give you a 'pdf' link alongside the output.