[TYPO3-content-rendering] Divide css_styled_content in multiple templates to rid ourselves of the compat versions

[Franz Koch]

Hi,
>> "# good old parsefunc in "styles.content.parseFunc" is created for 
>> backwards compatibility. Don't use it, just ignore.
>> styles.content.parseFunc < lib.parseFunc"
>>
> leave it.
> 
>> or the content element "splash". Should those be kept in the current 
>> version or can I discard them?
>>
> leave it, as you can activate splash if you want.

Then you can also add the needed TS-snippet ;)


shouldn't we take the opportunity and remove all the outdated 
HTML4-Markup and provide a clean and accessible XHTML version of CSC 
that can be used by default without rewriting major parts to get a clean 
output? Just like suggested in the tutorial on T3CON?

I don't see why we should keep that outdated stuff - who is using it 
anyway nowadays?

We could:
- drop the useless wraps around headlines and make them clean h-tags
- remove useless css-classes like <p class="bodytext"> (you can address 
those p-tags with nested CSS selectors)
- do we really need to show the prefixComments by default?
- do we really need all those csc-bulletlist and whatever classes?
- make forms more styleable and accessible and use ol/ul (there already 
was a discussion about that - but I can't remember in which group)
- integrate a up2date MULTIMEDIA component (damn - that one is really 
outdated)
- ...

-- 
kind regards,
Franz Koch