TYPO3 Core

I can't provide a patch yet as I wasn't able to "dig" into the TYPO3-Core for rendering Typoscript yet ;-)

I hope there will be a core-developer reading this who is able to provide a patch out of his hands very quick instead.

As long as you don't provide any data to be inserted within the dataWrap, you should not use it anyway.

10 = TEXT
10.dataWrap = {THIS SHOULD BE SHOWN AS TEXT WITH CURL}

no need for a dataWrap here, since this would be done by

10 = TEXT
10.value = {THIS SHOULD BE SHOWN AS TEXT WITH CURL}

same with the second example. There is no data to be inserted, so you should go for "value" instead of "dataWrap"

Of course there might be situations where you would have to insert data and use curly braces as well, but this could be solved easily like this:

10 = COA
10 {
10 = TEXT
10 {
field = fieldname
dataWrap = | {field:another_fieldname}
wrap3 = {|}
}
20 = TEXT
20 {
field = yet_another_fieldname
dataWrap = |{field:a_last_fieldname}
wrap3 = {|}
}
}

@ Jo Hasenau (reporter)

I totally agree, that some of my examples wouldn't need a dataWrap. These examples were not correct. In fact in each of the dataWrap's there should be any data-values which makes sense for the dataWrap-use instead of a plain value!

Thank you for your suggestion using wrap3 for the curls. But in fact there are situations which will make the typoscript unnessecarily blow-up because of that syntax. Imagine the rendering of more-complex javascript that has to be rendered using typoscript instead of static-inclusion. I don't think it would make sense to use hundred of COA and TEXT-wrap to solve the curls.

Of couse in usual way it makes sense to use static-external javascripts where ever possible. Also there shouldn't be more dataWrap than really needed (for performance reasons). But in some case this happens for complex data that has to be rendered into javascript-structures.

So why wouldn't it make sense to think about escaping for typoscript-internal values?

If you want to provide JavaScript with some values inserted, this would be a job for the TEMPLATE element. Just use your JS as the template file and fill in some markers to be replaced with the dynamic values.

Of course it could make sense to escape "internal" characters while parsing TypoScript, but I don't see too many use cases, that could not be solved easily with the current parser and some existing elements.