This is an automated email from the ASF dual-hosted git repository. ddekany pushed a commit to branch 2.3-gae in repository https://gitbox.apache.org/repos/asf/freemarker.git
commit 3f4fda52d067ab58afe9e2ffb4e0285d37f3308d Author: ddekany <[email protected]> AuthorDate: Tue Dec 24 09:56:56 2024 +0100 Manual: Updated release date, and some more version history adjustments --- freemarker-manual/src/main/docgen/en_US/book.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/freemarker-manual/src/main/docgen/en_US/book.xml b/freemarker-manual/src/main/docgen/en_US/book.xml index 08ca6b68..cbf1bffb 100644 --- a/freemarker-manual/src/main/docgen/en_US/book.xml +++ b/freemarker-manual/src/main/docgen/en_US/book.xml @@ -30458,7 +30458,7 @@ TemplateModel x = env.getVariable("x"); // get variable x</programlisting> <section xml:id="versions_2_3_34"> <title>2.3.34</title> - <para>Release date: 2024-12-08 + release process</para> + <para>Release date: 2024-12-22</para> <section> <title>Changes on the FTL side</title> @@ -30503,16 +30503,16 @@ TemplateModel x = env.getVariable("x"); // get variable x</programlisting> xlink:href="https://github.com/apache/freemarker/pull/119";>GitHub PR-119</link>: Fixed bug if you set the <link linkend="pgui_config_incompatible_improvements_how_to_set"><literal>incompatible_improvements</literal> - setting</link> to 2.3.34 or higher: Both - <literal>[#sep]</literal>, <literal><#sep></literal>, and + setting</link> to 2.3.34 or higher: <literal>[#sep]</literal>, + <literal><#sep></literal>, and <literal><sep></literal> were all interpreted as a call to the <literal>sep</literal> directive, regardless if the already established tag syntax was angle bracket or square bracket tags, or if the tag syntax was <quote>strict</quote> (requiring <literal>#</literal>) or not. With this fix enabled via <literal>incompatible_improvements</literal>, a - <literal>sep</literal> with the tag syntax that doesn't match - the configured/estabilished tag syntax will be seen as just + <literal>sep</literal> tag with the tag syntax that doesn't + match the configured/established tag syntax will be seen as just static text, just as it's done for any other FTL tags.</para> </listitem>
