Re: winehq: Fix some HTML markup
The reason I left the XHTML markup in was eventually the goal was to convert the entire website to XHTML. The only issue with leaving them in while still in HTML4/Transitional is that the pages do not pass W3C validation. I am still willing to live with non-valid working HTML to save some work down the road. -N André Hentschel wrote:
--- templates/de/about.template | 2 +- templates/de/contributing.template | 8 +++--- templates/de/download.template | 10 +++--- templates/de/help.template | 16 ++++++------ templates/en/about.template | 2 +- templates/en/contributing.template | 8 +++--- templates/en/documentation.template | 48 +++++++++++++++++----------------- templates/en/download.template | 10 +++--- templates/en/help.template | 16 ++++++------ templates/fr/about.template | 2 +- templates/pl/about.template | 2 +- templates/pl/download.template | 10 +++--- templates/pl/help.template | 16 ++++++------ templates/pt/about.template | 2 +- templates/pt/contributing.template | 8 +++--- 15 files changed, 80 insertions(+), 80 deletions(-)
------------------------------------------------------------------------
2009/9/10 Jeremy Newman <jnewman(a)codeweavers.com>:
The reason I left the XHTML markup in was eventually the goal was to convert the entire website to XHTML. The only issue with leaving them in while still in HTML4/Transitional is that the pages do not pass W3C validation. I am still willing to live with non-valid working HTML to save some work down the road.
XHTML is officially no longer developed - the future is HTML5, apparently. - d.
2009/9/10 David Gerard <dgerard(a)gmail.com>:
2009/9/10 Jeremy Newman <jnewman(a)codeweavers.com>:
The reason I left the XHTML markup in was eventually the goal was to convert the entire website to XHTML. The only issue with leaving them in while still in HTML4/Transitional is that the pages do not pass W3C validation. I am still willing to live with non-valid working HTML to save some work down the road.
XHTML is officially no longer developed - the future is HTML5, apparently.
XHTML 1.0 is essentially HTML as XML. Work on XHTML2 has stopped. HTML5 still supports the XML form (see http://www.w3.org/TR/html5/the-xhtml-syntax.html#the-xhtml-syntax) which supports XML namespaces (e.g. for MathML or SVG inline markup). - Reece
Reece Dunn wrote:
2009/9/10 David Gerard <dgerard(a)gmail.com>:
2009/9/10 Jeremy Newman <jnewman(a)codeweavers.com>:
The reason I left the XHTML markup in was eventually the goal was to convert the entire website to XHTML. The only issue with leaving them in while still in HTML4/Transitional is that the pages do not pass W3C validation. I am still willing to live with non-valid working HTML to save some work down the road. XHTML is officially no longer developed - the future is HTML5, apparently.
XHTML 1.0 is essentially HTML as XML. Work on XHTML2 has stopped. HTML5 still supports the XML form (see http://www.w3.org/TR/html5/the-xhtml-syntax.html#the-xhtml-syntax) which supports XML namespaces (e.g. for MathML or SVG inline markup).
I'm happy to see the more strict XHTML die. I preferred the looser flow of HTML4 anyway. -N
participants (3)
-
David Gerard -
Jeremy Newman -
Reece Dunn