[TYPO3-english] HTML5 & TYPO3

[Erik Svendsen]

I don't think this ever going to be any problem.

And TYPO3 isn't using proper XHTML, but XHTML coding style served as 
text/html. Proper XHTML has to be served as application/xhtml+xml.

Personally I find the debate between HTML and XHTML advocates more and 
less theoretical fuzz.

And HTML 5 will be both HTML 5 and XHTML 5, and you can serve it as 
text/html or application/xhtml+xml (with correct doctype). It will be no 
problem using XHTML coding style (closing tags, correct nesting) and 
using HTML 5 as doctype. A lot of developers are using HTML 4.01 Strict 
but the coding style of XHTML.

What's more important with (X)HTML 5 is new tags (elements) which has to 
be incorporated in part of TYPO3, for instance section, header, footer, 
nav (navigation menues), canvas. And some elements and attributes has to 
be removed. But TYPO3 could still choose to use XML syntax (coding 
style), and serve it as text/html.

But as (X)HTML 5 still are Working Draft, it will be years before it's 
implemented. Even newest versions of Presto, Gecko and WebKit has only 
partiall support, and IE will not have any support in at last 2 - 3 years.

Regards

Erik S

Jason Lefkowitz skrev:
> Hey everybody...
> 
> For as long as I've been using TYPO3, it has seemed very oriented 
> towards using XHTML as its chosen markup syntax. See, for example, how 
> CONFIG.doctype provides options for setting your site's DOCTYPE 
> declaration to any flavor of XHTML you wish, but does not include 
> options for HTML 4; or how TYPO3 uses XML-style element closures by 
> default (e.g. "<br />" rather than "<br>").
> 
> A few weeks ago, however, the W3C essentially deprecated XHTML as a 
> standard by closing down the XHTML2 Working Group and encouraging 
> interested parties to take up the still-in-progress HTML5 spec instead. 
> (See http://www.w3.org/2009/06/xhtml-faq for details.) While HTML5 will 
> offer an XHTML-style XML serialization, it's becoming pretty clear that 
> this "flavor" of HTML5 will not be the primary one developers will be 
> using.
> 
> Has anyone articulated yet how TYPO3 will be making the move to HTML5, 
> and what work will be required on the part of TYPO3 admins & developers 
> to make that move happen? I've been looking for this kind of information 
> but haven't seen it anywhere, so links, suggestions, etc. will be 
> gratefully appreciated...
> 
> -- Jason