[TYPO3-dev] RFC: Change roadmap for 4.5 and 5.0

[Michael Scharkow]

Christopher wrote:

> I'm honestly bewildered by the claim that it's difficult to switch
> between xhtml and html in code generation: given that TYPO3, when it
> outputs markup at all, is not checking for validity or
> well-formedness, the entire extent of the problem is limited to
> doctypes, the decision to include--or not--closing tags on 'empty'
> elements, and differences in attributes (e.g. target and border). If a
> doctype is set using ' config.doctype = ___ ' then a simple check
> seems to be all that's needed when outputting closing slashes and
> attributes. And there are only a few elements where even _this_ would
> be needed (meta, img, br, base...)

I agree that the problem itself is trivial: You simply check if 
xhtml==true and add a slash, or sth. like that. But if you want this 
feature to be used consistently, you have to abstain from writing any of 
the concerned tags in your views, be it in hardcoded php or some 
template language. Instead, you're forced to write wrappers like 
renderTag('img',$src='foo', $class='bar') which I don't find 
particularly elegant, but some die-hard JAVA users or TS gurus might.

Alternatives would be a) post-processing of output (aargh), b) separate 
templates for HTML and XHMTL (like to different versions of CSC) which 
does not scale very well, c) choosing just one supported HTML version.

I could not care less about whether to use HTML or XHTML in whatever 
version (unless there are some legal requirements for this, as I vaguely 
remember in Germany's BITV, might be wrong though) as long as we don't 
need to support two incompatible versions.

Greetings,
Michael