TYPO3.Fluid

yes it is a copy of CDATA but most convenient:

CDATA:
<![CDATA[{]]>{object}<![CDATA[}]]> renders to {value}

vs

escape sequenze:
\{{object}\} renders to {value}

Bastian SGML/HTML/XML entity will not work
output is

and i think this is good so as it is -> maybe you need to print SGML/HTML/XML to

Escape sequence is usefull for StandaloneView.
Here is a demo
1 /** 2 * An example command to render views with escape sequenze 3 * 4 * This renders a view with Fluid to String and print this to your shell 5 * 6 * @return void 7 */ 8 public function escapeSequenzeDemoCommand() { 9 10 $templateSource = ' 11cdata <![CDATA[{]]>{object.property1}<![CDATA[}]]> 12escapeSequence \{{object.property1}\} 13 <!\[CDATA[\{]]>{object.property1}<!\[CDATA[\}]] 14 <!\[CDATA[{]]>{object.property1}<!\[CDATA[}]] 15XML entity &#123;{object.property1}&#125; 16'; 17 18 $view = new \TYPO3\Fluid\View\StandaloneView(); 19 $view->setTemplateSource($templateSource); 20 21 $object = array('property1' => 'value'); 22 $view->assign('object', $object); 23 echo $view->render() . PHP_EOL; 24 25 }

output:

TBH I just discovered another use case for my very own, I needed to

1<f:form.hidden name="message[recipient]" value="{recipientIdentifier}" />

while the value should literally be {recipientIdentifier} (it's for JavaScript substitution lateron).
Any ideas how to achieve this currently?

Adrian Föder wrote:

TBH I just discovered another use case for my very own, I needed to

[...]

while the value should literally be {recipientIdentifier} (it's for JavaScript substitution lateron).
Any ideas how to achieve this currently?

currently you can use CDATA

i tried your example with my solution of escape sequenze as follows:

and Fluid prints:

with on https://gist.github.com/RafaelKa/5159642 code kickstarter breaks

to

in
https://gist.github.com/RafaelKa/5232405

i added a list of to escaped characters [ ] { } \

are there some more characters to be escaped by Fluid?

Rafael Kähm wrote:

with on https://gist.github.com/RafaelKa/5159642 code kickstarter breaks

1... 2> use TYPO3\Flow\Annotations as Flow; 3> ...

to

1... 2> use TYPO3FlowAnnotations as Flow; 3> ...

in
https://gist.github.com/RafaelKa/5232405

i added a list of to escaped characters [ ] { } \

are there some more characters to be escaped by Fluid?

This works as well (I know that is not so clean but):

In the controller:

$this->view->assign('oBrc', '{');
$this->view->assign('cBrc', '}');

In the view:

{oBrc}MyValue{cBrc}

you can write the literal closing brace and you obtain the same value. Like this:

{oBrc}MyValue}

The use case that Adrian points out can be worked out in a simpler way like this:
controller:

$this->view->assign('recipientIdentifier', '{recipientIdentifier}');

view:

<f:form.hidden name="message[recipient]" value="{recipientIdentifier}" />

Of course if you have to print out many literal values (or to produce for example a JSON template) the ability to escape braces would be the best way to achieve it.

Tarcisio Fedrizzi wrote:

This works as well (I know that is not so clean but):

In the controller:
[...]

In the view:
[...]

you can write the literal closing brace and you obtain the same value. Like this:

[...]

The use case that Adrian points out can be worked out in a simpler way like this:
controller:
[...]

view:
[...]

Of course if you have to print out many literal values (or to produce for example a JSON template) the ability to escape braces would be the best way to achieve it.

I think this is currently the most usable workaround. But instead of using a controller you can also use f:alias in a template.

<f:alias map="{ocb: '{', ccb: '}'}">
    <f:uri.action arguments="{start: '{ocb}start{ccb}'}" [...] />
</f:alias>

Anyway such a feature would make some templates much more cleaner.

To my eyes, it would be better to escape single { characters, so one can still use Fluid variables inside a pair of escaped curly braces.

As an example, I am trying to use Fluid to produce some CSS code like this:

<n:headerData>
    <style type="text/css">
        .article-{newsItem.uid} \{
            background-image: url('{f:uri.image(src: "{mediaElement.uid}")}');
        \}
    </style>
</n:headerData>

This would not work with the \{escaped} approach.

@Hannes: An escaped opening brace \{ can immediately be followed by another opening brace (for the variable). So imho you could do: \{{variable}}
It could be discussed whether escaping the closing brace as well would make it easier to read. But it's not mandatory since with no active opening brace at that point the closing brace is just regarded as text.