[TYPO3-RTE] links and <p> in Tablecells and hello to the list

[Steffen Kamper]

Hi Uschi - and welcome !

Your annotations are very interesting. I also searched in the source - but 
my be from the wrong way (pagegen).

Your solution is very plausible and I will test it.
But for all that it is a bug and sometimes it's useful to use the 
destructive way.

mg
Steffen

"Uschi Renziehausen" <typo3news at otherone.de> schrieb im Newsbeitrag 
news:mailman.1.1149363255.29970.typo3-project-rte at lists.netfielders.de...
>A friendly hello to this list from a latin teacher at the university of 
>Erfurt (Germany) and some (hopefully usefull) remarks on <p> in table 
>cells.
>
> The two solutions mentioned here are both destructive in a way:
> > lib.parseFunc_RTE.externalBlocks.table.stdWrap.HTMLparser.removeTags = p
> This will ask the parser to remove each and every <p>-Element from table 
> cells, even those the author wanted.
> >
> lib.parseFunc_RTE.externalBlocks.table.HTMLtableCells.default.callRecursive 
> = 0
> is even more destructive, since it causes the parser to do nothing at all 
> with the content of a table cell, and this is why the links get lost.
>
> So I had a closer look at lib.parseFunc_RTE (defined in 
> EXT:css_styled_content/static/setup.txt) in order to find out, where the 
> magical p comes in. The relevant lines are found inside the object path 
> lib.parseFunc_RTE.externalBlocks:
>
>  table.HTMLtableCells=1
>  table.HTMLtableCells {
> default.callRecursive=1
> addChr10BetweenParagraphs=1
>  }
>
>
> Line 3 means: Let the content of table cells go through lib.parseFunc_RTE 
> again, because this is the parser function we are currently in, and 
> consequently also the nonTypoTagStdWrap.encapsLines - section a few lines 
> further down will be executed, and there the parser is told to wrap 
> everything which is not wrapped in <div> or <p> already with a <p>:
> lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.nonWrappedTag = P
>
> It is no solution to just empty this line, because this would affect 
> normal bodytext as well, and so I tried to find out, where the links are 
> transformed from <link> to <a>. This is done in lib.parseFunc. So i ended 
> up in a two line TS solution.
>
> lib.parseFunc_RTE.externalBlocks.table.HTMLtableCells.default >
> lib.parseFunc_RTE.externalBlocks.table.HTMLtableCells.default.stdWrap.parseFunc 
> =< lib.parseFunc
>
> Everything seems to work fine: The <p>-Elements I entered deliberately are 
> kept, no magical ones are added, and my links are transformed properly.
>
> Ciao, Uschi
>