[
https://issues.apache.org/jira/browse/VELOCITY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475613
]
Nathan Bubna commented on VELOCITY-519:
---------------------------------------
No, it's not backwards compatible. The unicode escapes are merely by virtue of
the fact that they caused an error previously. \n \r and \t are not backwards
compatible. And if you want to insert one of those characters, just insert
them in the string. There's no need to enter it in escaped form and then make
Velocity convert for you when you can just put the character in the string
yourself. No tools or patches necessary here, and definitely no need to break
backwards compatibility.
> Java escape sequences should work in Velocity macros
> ----------------------------------------------------
>
> Key: VELOCITY-519
> URL: https://issues.apache.org/jira/browse/VELOCITY-519
> Project: Velocity
> Issue Type: New Feature
> Affects Versions: 1.5 beta2
> Reporter: Stepan Koltsov
> Attachments: velocity-unescape-2007-02-24-stepancheg.diff,
> velocity-unescape-only-u-2007-02-24-stepancheg.diff
>
>
> Following test should work:
> ===
> public void testJavaEscape() throws Exception {
> VelocityEngine ve = new VelocityEngine();
> ve.init();
> Context context = new VelocityContext();
> StringWriter writer = new StringWriter();
> ve.evaluate(context, writer, "test","#set($v = \"\\u0061\")$v");
> assertEquals("a", writer.toString());
> writer = new StringWriter();
> ve.evaluate(context, writer, "test","#set($v = \"\\n\")$v");
> assertEquals("\n", writer.toString());
> }
> ===
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
