Re: texi2html output validity

[Gavin Smith]

>         The problem is that for a couple of months now, the most recent
>         HTML version is HTML5, and it does /not/ specify these elements.
>
>         Granted, there’re browsers which still support these, but I
>         could easily imagine a new browser project being started that
>         would just ignore all the cruft that was already scheduled to be
>         removed back in the 20th century.
>
We're not bound to follow the latest HTML standard. If there become
incompatibilities between more popular, newer and more
standards-conformant browsers which are impractical to account for in
the HTML output, or if such incompatibilities exist at the moment,
then of course we should target what is the most common. At the moment
though it doesn't seem that inconvenient to provide for browsers with
limited CSS support or lacking support for newer tags.