aboutsummaryrefslogtreecommitdiffstats
path: root/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md')
-rw-r--r--vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md36
1 files changed, 36 insertions, 0 deletions
diff --git a/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md b/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md
new file mode 100644
index 000000000..27ebb3ff4
--- /dev/null
+++ b/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-literal.md
@@ -0,0 +1,36 @@
+{literal} {#language.function.literal}
+=========
+
+`{literal}` tags allow a block of data to be taken literally. This is
+typically used around Javascript or stylesheet blocks where {curly
+braces} would interfere with the template
+[delimiter](#variable.left.delimiter) syntax. Anything within
+`{literal}{/literal}` tags is not interpreted, but displayed as-is. If
+you need template tags embedded in a `{literal}` block, consider using
+[`{ldelim}{rdelim}`](#language.function.ldelim) to escape the individual
+delimiters instead.
+
+> **Note**
+>
+> `{literal}{/literal}` tags are normally not necessary, as Smarty
+> ignores delimiters that are surrounded by whitespace. Be sure your
+> javascript and CSS curly braces are surrounded by whitespace. This is
+> new behavior to Smarty 3.
+
+
+ <script>
+ // the following braces are ignored by Smarty
+ // since they are surrounded by whitespace
+ function myFoo {
+ alert('Foo!');
+ }
+ // this one will need literal escapement
+ {literal}
+ function myBar {alert('Bar!');}
+ {/literal}
+ </script>
+
+
+
+See also [`{ldelim} {rdelim}`](#language.function.ldelim) and the
+[escaping Smarty parsing](#language.escaping) page.