[TYPO3-english] HTML5 & TYPO3

Jason Lefkowitz jason at jasonlefkowitz.net
Tue Jul 28 18:43:28 CEST 2009


 > Well, then let "the developers" use plain-sucky HTML5 and we'll stick 
to the XML variant. Agreed?

I agree that there's lots of things in HTML5 as it stands now that are 
not very elegant. But I don't understand why there's pushback against 
moving away from the "XHTML Or Nothing" mentality.

Plain old HTML 4.01 is completely fine from a standards-compliance 
perspective, *if* you write it correctly. It is arguably MORE standards 
compliant than serving XHTML without the proper MIME type, which is what 
the vast majority of TYPO3 sites that have XHTML DOCTYPEs do.  (The rest 
are usually even worse -- see typo3.org, for instance, which uses the 
HTML 4.01 DOCTYPE, but then uses XHTML style for its tags.)

My concern is that the default configuration for TYPO3 is to generate 
sites that are not standards-compliant, which is the exact opposite of 
how it should be. TYPO3 should make it easy to do things right and hard 
to do things wrong, not the other way around. The official death of 
XHTML gives us an opportunity to move in that direction.

-- Jason

(who'd be happy to help in that effort, just tell him how)



Karsten Dambekalns wrote:
> Hi.
> 
> On 27.07.09 15:23, Jason Lefkowitz wrote:
>> (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.
> 
> Well, then let "the developers" use plain-sucky HTML5 and we'll stick to 
> the XML variant. Agreed?
> 
> I will never understand what is so much better about that old-school 
> HTML5 variant. I looked at some source code, and it's just cruel...
> 
> Regards,
> Karsten
> 
> PS: This is not an official statement :)


More information about the TYPO3-english mailing list