In HTML, the TBODY element is inferred, even if it is not present in the markup of a table. In XHTML, that is not true. What will happen here? Will your aggregator treat the following table as XHTML?
This text should not be green! |
If the above text was green, then your aggregator is ignoring the explicit
injunction that the content of this entry is of type="xhtml"
and is,
instead, treating it as tag-soup.
In HTML, element names are case-insensitive and namespaces are not supported. In XHTML, the opposite is true. What will happen here?
This sentence should not
be bold.
If the above text was incorrectly-bolded, then your aggregator is
ignoring the explicit injunction that the content of this
entry is of type="xhtml"
and is, instead, treating it
as tag-soup.
If your aggregator failed the XHTML test, then you haven't a prayer of this one succeeding. That requires that your aggregator treats the content here as XHTML and that it support MathML. Thunderbird is a Mozilla product. So it has a fighting chance to pass this test. As far as I know, it fails.
Was that good for you?
I use SVG for figures. For those without the Adobe SVG plugin (or native SVG support in the client), I use a GIF image as a fallback. If you see the SVG image, but it's screwed up, then the native SVG support in your aggregator's rendering engine is buggy and substandard. If your aggregator's rendering engine doesn't support SVG, it should display the fallback GIF image instead. Most likely, however, you see nothing at all.