[TYPO3-RTE] Table in Unordered List

[Uschi Renziehausen]

Hi Tapio,

>>
>> 1) Are you using the same TYPO3 versions?
> 
> apparently not I tested with Typo3 4.1 and Ushi apparently 4.2.x
> That might have some Typo3 related default config differencies but if 
> all needed has been reset the difference should not then affect.
>

While I am in doubt whether or not different RTEs make a lot of 
difference (I am an rtehtmlarea addict, because you can really make it a 
html editor with all tags at hand and a nifty class handling + a quite 
comfortable table editor including zebra tables), but I am absolutely 
sure that the central htmlparser has changed from 4.1 to 4.2, especially 
when dealing with block elements. In 4.2 you can have p AND div elements 
and the whole thing is a lot more reasonable.

Prosit, Uschi



> I looked differencies, which might have some effect:
> 
> 
> tt_content.table {
>     10 = < lib.stdheader
> 
>     20 = USER
>     20.userFunc = tx_cssstyledcontent_pi1->render_table
> #this doesn't exist in 4.1 but apparently this is not meaningsful?
>     20.field = bodytext
> 
> and these
> 
> # new RTE indentation using div element
> [compatVersion = 4.2.0]
> 
> lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.encapsTagList := 
> removeFromList(div)
> lib.parseFunc_RTE.externalBlocks := addToList(div)
> lib.parseFunc_RTE.externalBlocks.div.stripNL = 1
> lib.parseFunc_RTE.externalBlocks.div.callRecursive = 1
> 
> [END]
> 
> All mentioned in [compatVersion = 4.2.0] has been defined in the root TS 
> template for lib.parseFunc_RTE - there is no differencies.
> 
> BTW. It might be reasonable to add for tinymce_rte some more TS
> 
>> 2) Are you using the same RTE editor?
> 
> apparently not but I just presume that RTE db field > FE transformation 
> would be the same
> 
> TS config for pages handles RTE field > db and db > RTE field conversions,
> but that should not affect RTE db field transformation, which relates 
> with lib.parseFunc_RTE. Or does it?