[
https://issues.apache.org/jira/browse/VELOCITY-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475618
]
Will Glass-Husain commented on VELOCITY-519:
--------------------------------------------
That's a good point. If the \u00b1 format didn't work at all before, there's
no harm in adding it in. And it adds new capability. (inserting characters
into the body that you might not have been able to before).
But if \t, \r, \n were were just passed through (and possibly this was desired
by someone generating Java code) we shouldn't intercept it. So I withdraw my
suggestion for \t, \r, \n parsing.
> 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]
