Synopsis: exp?substring(from, toExclusive), also callable as exp?substring(from)

A substring of the string. from is the index of the first character. It must be a number that is at least 0 and less than or equal with toExclusive, or else an error will abort the template processing. The toExclusive is the index of the character position after the last character of the substring, or with other words, it is one greater than the index of the last character. It must be a number that is at least 0 and less than or equal to the length of the string, or else an error will abort the template processing. If the toExclusive is omitted, then it defaults to the length of the string. If a parameter is a number that is not an integer, only the integer part of the number will be used.

Example:

	- ${'abc'?substring(0)} - ${'abc'?substring(1)} - ${'abc'?substring(2)} - ${'abc'?substring(3)} - ${'abc'?substring(0, 0)} - ${'abc'?substring(0, 1)} - ${'abc'?substring(0, 2)} - ${'abc'?substring(0, 3)} - ${'abc'?substring(0, 1)} - ${'abc'?substring(1, 2)} - ${'abc'?substring(2, 3)}

The output:

	- abc - bc - c - - - a - ab - abc - a - b - c

The string with the very first word of the string capitalized. For the precise meaning of ``word'' see the word_list built-in. Example:

	${" green mouse"?cap_first} ${"GreEN mouse"?cap_first} ${"- green mouse"?cap_first}

The output:

	Green mouse GreEN mouse - green mouse

In the case of "- green mouse", the first word is the -.

The opposite of cap_first. The string with the very first word of the string un-capitalized.

The string with all words capitalized. For the precise meaning of ``word'' see the word_list built-in. Example:

	${" green mouse"?capitalize} ${"GreEN mouse"?capitalize}

The output:

	Green Mouse Green Mouse

The string without the line-break at its very end if there was a line-break, otherwise the unchanged string.

The string converted to a date value. It is recommended to specify a parameter that specifies the format. For example:

	<#assign test1 = "10/25/1995"?date("MM/dd/yyyy")> <#assign test2 = "15:05:30"?time("HH:mm:ss")> <#assign test3 = "1995-10-25 03:05 PM"?datetime("yyyy-MM-dd hh:mm a")> ${test1} ${test2} ${test3}

will print something like (depends on the output locale (language) and on other settings):

	Oct 25, 1995 3:05:30 PM Oct 25, 1995 3:05:00 PM

Note that the dates was converted back to string according to the date_format, time_format and datetime_format settings (for more information about converting dates to strings read: string built-in for dates, date interpolations). It does not mater what format did you use when you have converted the strings to dates.

You don't have to use the format parameter, if you know what the default date/time/datetime format will be when the template is processed:

	<#assign test1 = "Oct 25, 1995"?date> <#assign test2 = "3:05:30 PM"?time> <#assign test3 = "Oct 25, 1995 03:05:00 PM"?datetime> ${test1} ${test2} ${test3}

If the string is not in the appropriate format, an error will abort template processing when you try to access this built-in.

Returns if this string ends with the specified substring. For example "redhead"?ends_with("head") returns boolean true. Also, "head"?ends_with("head") will return true.

The string as HTML markup. That is, the string with all:

Note that if you want to insert an attribute value securely, you must quote the attribute value in the HTML template with quotation mark (with ", not with '):

	<input type=text name=user value="${user?html}">

Note that in HTML pages usually you want to use this built-in for all interpolations. So you can spare a lot of typing and lessen the chances of accidental mistakes by using the escape directive.

This is used only with the result of the matches built-in. See there...

Returns the index within this string of the first occurrence of the specified substring. For example, "abcabc"?index_of("bc") will return 1 (don't forget that the index of the first character is 0). Also, you can specify the index to start the search from: "abcabc"?index_of("bc", 2) will return 4. There is no restriction on the numerical value of the second parameter: if it is negative, it has the same effect as if it were zero, and if it is greater than the length of this string, it has the same effect as if it were equal to the length of this string. Decimal values will be truncated to integers.

If the 1st parameter does not occur as a substring in this string (starting from the given index, if you use the second parameter), then it returns -1.

Escapes the string with the escaping rules of Java language string literals, so it is safe to insert the value into a string literal. In additional, all characters under UCS code point 0x20, that has no dedicated escape sequence in Java language, will be replaced with UNICODE escape (\uXXXX).

Example:

	<#assign beanName = 'The "foo" bean.'> String BEAN_NAME = "${beanName?j_string}";

will output:

	String BEAN_NAME = "The \"foo\" bean.";

Escapes the string with the escaping rules of JavaScript language string literals, so it is safe to insert the value into a string literal. Both quotation mark (") and apostrophe-quoate (') are escaped. Starting from FreeMarker 2.3.1, it also escapes > as \> (to avoid </script>). Furthermore, all characters under UCS code point 0x20, that has no dedicated escape sequence in JavaScript language, will be replaced with hexadecimal escape (\xXX). (Of course, according the JavaScript language string literal syntax, backslash (\) will be escaped too, line-feed will be escaped as \n, ...etc.)

Example:

	<#assign user = "Big Joe's \"right hand\""> <script> alert("Welcome ${user?js_string}!"); </script>

will output:

	<script> alert("Welcome Big Joe\'s \"right hand\"!"); </script>

Returns the index within this string of the last (rightmost) occurrence of the specified substring. It returns the index of the first (leftmost) character of the substring. For example: "abcabc"?last_index_of("ab") will return 3. Also, you can specify the index to start the search from. For example, "abcabc"?last_index_of("ab", 2) will return 0. Note that the second parameter indicates the maximum index of the start of the substring. There is no restriction on the numerical value of the second parameter: if it is negative, it has the same effect as if it were zero, and if it is greater than the length of this string, it has the same effect as if it were equal to the length of this string. Decimal values will be truncated to inegers.

If the 1st parameter does not occur as a substring in this string (before the given index, if you use the second parameter), then it returns -1.

The number of characters in the string.

The lower case version of the string. For example "GrEeN MoUsE" will be "green mouse".

If it's used with 1 parameter, then it inserts spaces on the beginning of the string until it reaches the length that is specified as the parameter. If the string is already as long or longer than the specified length, then it does nothing. For example, this:

	[${""?left_pad(5)}] [${"a"?left_pad(5)}] [${"ab"?left_pad(5)}] [${"abc"?left_pad(5)}] [${"abcd"?left_pad(5)}] [${"abcde"?left_pad(5)}] [${"abcdef"?left_pad(5)}] [${"abcdefg"?left_pad(5)}] [${"abcdefgh"?left_pad(5)}]

will output this:

	[ ] [ a] [ ab] [ abc] [ abcd] [abcde] [abcdef] [abcdefg] [abcdefgh]

If it's used with 2 parameters, then the 1st parameter means the same as if you were using the built-in with only 1 parameter, and the second parameter specifies what to insert instead of space characters. For example:

	[${""?left_pad(5, "-")}] [${"a"?left_pad(5, "-")}] [${"ab"?left_pad(5, "-")}] [${"abc"?left_pad(5, "-")}] [${"abcd"?left_pad(5, "-")}] [${"abcde"?left_pad(5, "-")}]

will output this:

	[-----] [----a] [---ab] [--abc] [-abcd] [abcde]

The 2nd parameter can be a string whose length is greater than 1. Then the string will be inserted periodically, for example:

	[${""?left_pad(8, ".oO")}] [${"a"?left_pad(8, ".oO")}] [${"ab"?left_pad(8, ".oO")}] [${"abc"?left_pad(8, ".oO")}] [${"abcd"?left_pad(8, ".oO")}]

will output this:

	[.oO.oO.o] [.oO.oO.a] [.oO.oOab] [.oO.oabc] [.oO.abcd]

The 2nd parameter must be a string value, and it must be at least 1 character long.

This is the same as left_pad, but it inserts the characters at the end of the string instead of the beginning of the string.

Example:

	[${""?right_pad(5)}] [${"a"?right_pad(5)}] [${"ab"?right_pad(5)}] [${"abc"?right_pad(5)}] [${"abcd"?right_pad(5)}] [${"abcde"?right_pad(5)}] [${"abcdef"?right_pad(5)}] [${"abcdefg"?right_pad(5)}] [${"abcdefgh"?right_pad(5)}] [${""?right_pad(8, ".oO")}] [${"a"?right_pad(8, ".oO")}] [${"ab"?right_pad(8, ".oO")}] [${"abc"?right_pad(8, ".oO")}] [${"abcd"?right_pad(8, ".oO")}]

This will output this:

	[ ] [a ] [ab ] [abc ] [abcd ] [abcde] [abcdef] [abcdefg] [abcdefgh] [.oO.oO.o] [aoO.oO.o] [abO.oO.o] [abc.oO.o] [abcdoO.o]

Returns if the substring specified as the parameter to this built-in occurrs in the string. For example:

	<#if "piceous"?contains("ice")>It contains "ice"</#if>

This will output:

	It contains "ice"

This is a ``power user'' built-in. Ignore it if you don't know regular expressions.

This built-in determines if the string exactly matches the pattern. Also, it returns the list of matching sub-strings. The return value is a multi-type value:

For example:

	<#if "fxo"?matches("f.?o")>Matches.<#else>Does not match.</#if> <#assign res = "foo bar fyo"?matches("f.?o")> <#if res>Matches.<#else>Does not match.</#if> Matching sub-strings: <#list res as m> - ${m} </#list>

will print:

	Matches. Does not match. Matching sub-strings: - foo - fyo

If the regular expression contains groups (parentheses), then you can access them with the groups built-in:

	<#assign res = "aa/rx; ab/r;"?matches("(\\w[^/]+)/([^;]+);")> <#list res as m> - ${m} is ${m?groups[1]} per ${m?groups[2]} </#list>

This will print:

	- aa/rx; is aa per rx - ab/r; is ab per r

matches accepts an optional 2nd parameter, the flags. Note that it does not support flag r, because it always uses regular expressions.

The string converted to numerical value. The number must be in the same format as you specify numerical values directly in FTL. That is, it must be in the locale independent form, where the decimal separator is dot. In additional the built-in recognizes scientific notation (e.g. "1.23E6", "1.5e-8").

If the string is not in the appropriate format, an error will abort template processing when you try to access this built-in.

Known problem: If you use earlier Java2 platform than v1.3, the built-ins will not recognize + prefix and scientific notation.

It is used to replace all occurrences of a string in the original string with another string. It does not deal with word boundaries. For example:

	${"this is a car acarus"?replace("car", "bulldozer")}

will print:

	this is a bulldozer abulldozerus

The replacing occurs in left-to-right order. This means that this:

	${"aaaaa"?replace("aaa", "X")}

will print:

	Xaa

If the 1st parameter is an empty string, then all occurrences of the empty string will be replaced, like "foo"?replace("","|") will evaluate to "|f|o|o|".

replace accepts an optional flags parameter, as its 3rd parameter.

The string as Rich text (RTF text). That is, the string with all:

The string after URL escaping. This means that all non-US-ASCII and reserved URL characters will be escaped with %XX. For example:

	<#assign x = 'a/b c'> ${x?url}

The output will be (assuming that the charset used for the escaping is an US-ASCII compatible charset):

	a%2Fb%20c

Note that it escapes all reserved URL characters (/, =, &, ...etc), so this encoding can be used for encoding query parameter values, for example:

	<a href="foo.cgi?x=${x?url}&y=${y?url}">Click here...</a>

To do URL escaping a charset must be chosen that will be used for calculating the escaped parts (%XX). If you are HTML page author and you don't really understand this, don't worry: the programmers should configure FreeMarker so that it uses the proper charset by default (programmers: see more below...). If you are a more technical minded user, then you may want to know that the charset used is specified by the url_escaping_charset setting, that can be set in template execution time (or, preferably, earlier by the programmers). For example:

	<#-- This will use the charset specified by the programmers before the template execution has started. --> <a href="foo.cgi?x=${x?url}">foo</a> <#-- Use UTF-8 charset for URL escaping from now: --> <#setting url_escaping_charset="UTF-8"> <#-- This will surely use UTF-8 charset --> <a href="bar.cgi?x=${x?url}">bar</a>

Furthermore, you can explicitly specify a charset for a single URL escaping as the parameter to the built-in:

	<a href="foo.cgi?x=${x?url('ISO-8895-2')}">foo</a>

If the url built-in has no parameter, then it will use the charset specified as the value of the url_escaping_charset setting. This setting should be set by the software that encloses FreeMarker (e.g. a Web application framework), because it is not set (null) by default. If it is not set, then FreeMarker falls back using the value of the output_encoding setting, which is also not set by default, so it is again the task of the enclosing software. If the output_encoding setting is not set either, then the parameterless url built-in can't be executed, and it will cause execution time error. Of course, the url built-in with parameter always works.

It's possible to set url_escaping_charset in the template with the setting directive, but it is bad practice, at least in true MVC applications. The output_encoding setting can't be set with the setting directive, so that's surely the task of the enclosing software. You may find more information regarding this here...

It is used to split a string into a sequence of strings along the occurrences of another string. For example:

	<#list "someMOOtestMOOtext"?split("MOO") as x> - ${x} </#list>

will print:

	- some - test - text

Note that it is assumed that all occurrences of the separator is before a new item, thus:

	<#list "some,,test,text,"?split(",") as x> - "${x}" </#list>

will print:

	- "some" - "" - "test" - "text" - ""

split accepts an optional flags parameter, as its 2nd parameter.

Returns if this string starts with the specified substring. For example "redhead"?starts_with("red") returns boolean true. Also, "red"?starts_with("red") will return true.

Does nothing, just returns the string as-is. The exception is that if the value is a multi-type value (e.g. it is both string and sequence at the same time), then the resulting value will be only a simple string, not a multi-type value. This can be utilized to prevent the artifacts of multi-typing.

The string without leading and trailing white-space. Example:

	(${" green mouse "?trim})

The output:

	(green mouse)

The upper case version of the string. For example "GrEeN MoUsE" will be "GREEN MOUSE".

A sequence that contains all words of the string in the order as they appear in the string. Words are continual character sequences that contain any character but white-space. Example:

	<#assign words = " a bcd, . 1-2-3"?word_list> <#list words as word>[${word}]</#list>

will output:

	[a][bcd,][.][1-2-3]

The string as XML text. That is, the string with all:

Many string built-ins accept an optional string parameter, the so called ``flags''. In this string, each letter influences a certain aspect of the behavior of the built-in. For example, letter i means that the built-in should not differentiate the lower and upper-case variation of the same letter. The order of the letters in the flags string is not significant.

This is the complete list of letters (flags):

Example:

	<#assign s = 'foo bAr baar'> ${s?replace('ba', 'XY')} i: ${s?replace('ba', 'XY', 'i')} if: ${s?replace('ba', 'XY', 'if')} r: ${s?replace('ba*', 'XY', 'r')} ri: ${s?replace('ba*', 'XY', 'ri')} rif: ${s?replace('ba*', 'XY', 'rif')}

Prints:

	foo bAr XYar i: foo XYr XYar if: foo XYr baar r: foo XYAr XYr ri: foo XYr XYr rif: foo XYr baar

This is the table of built-ins that use these common flags, and which supports which flags: