(freemarker) branch 2.3-gae updated: Javadoc: Fixed malformed HTML

[dd...@apache.org]

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


The following commit(s) were added to refs/heads/2.3-gae by this push:
     new 0c85748f Javadoc: Fixed malformed HTML
0c85748f is described below

commit 0c85748f0b4eee8a002b15ac4642a1f49a066631
Author: ddekany <dd...@apache.org>
AuthorDate: Tue Dec 24 10:45:16 2024 +0100

    Javadoc: Fixed malformed HTML
---
 .../main/java/freemarker/template/Configuration.java    | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/freemarker-core/src/main/java/freemarker/template/Configuration.java b/freemarker-core/src/main/java/freemarker/template/Configuration.java
index be0bb482..fcafff7d 100644
--- a/freemarker-core/src/main/java/freemarker/template/Configuration.java
+++ b/freemarker-core/src/main/java/freemarker/template/Configuration.java
@@ -995,7 +995,7 @@ public class Configuration extends Configurable implements Cloneable, ParserConf
      *           characters were treated as equal by the collator, but will count as different now. But it's very
      *           unlikely that anyone wanted to depend on such fragile logic anyway. Note again that we still do UNICODE
      *           normalization, so combining characters won't break your comparisons.)</p></li>
-     *       <li><p>
+     *         <li><p>
      *          The default {@link Configuration#setObjectWrapper(ObjectWrapper) object_wrapper} now exposes Java
      *          records public methods with 0-arguments and non-void return type are now exposed both as properties,
      *          and as methods; see {@link BeansWrapper#BeansWrapper(Version)}.
@@ -1005,14 +1005,13 @@ public class Configuration extends Configurable implements Cloneable, ParserConf
      *       <p>
      *       2.3.34 (or higher):
      *       <ul>
-     *       <li><p>
-     *          Fixes this parser bug, which can break already incorrect templates that accidentally worked so far:
-     *          {@code [#sep]}, {@code <#sep>}, and {@code <sep>} were all interpreted as a call to the {@code sep}
-     *          directive, regardless if the already established tag syntax was angle bracket or square bracket tags, or
-     *          if the tag syntax was strict (requiring {@code #}) or not. With this fix enabled, a {@code sep} 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.
-     *       </ul>
+     *         <li><p>
+     *           Fixes this parser bug, which can break already incorrect templates that accidentally worked so far:
+     *           {@code [#sep]}, {@code <#sep>}, and {@code <sep>} were all interpreted as a call to the {@code sep}
+     *           directive, regardless if the already established tag syntax was angle bracket or square bracket tags, or
+     *           if the tag syntax was strict (requiring {@code #}) or not. With this fix enabled, a {@code sep} 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.
      *       </ul>
      *   </li>
      * </ul>