[
https://issues.apache.org/jira/browse/VELOCITY-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna updated VELOCITY-229:
----------------------------------
Fix Version/s: (was: 1.6)
descheduling until/unless we get the legal issue handled. i'm also not sure
what the status of this with regard to the related issues VELOCITY-101 and
VELOCITY-451. This issue needs someone to properly champion it, as Charles
seems to have disappeared.
> Velocity templates should be able to specify their own encoding
> ---------------------------------------------------------------
>
> Key: VELOCITY-229
> URL: https://issues.apache.org/jira/browse/VELOCITY-229
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Affects Versions: 1.5
> Environment: Operating System: All
> Platform: All
> Reporter: Charles Morehead
> Priority: Minor
> Attachments: encoding-support.jar, Template.diff
>
>
> Velocity templates should be able to specify their own encoding without
> requiring external knowledge of the encoding before parsing (as least
> for all ASCII-compatible encodings). Many other scripting/templating
> systems (like JSP and python, for example) provide such a mechanism,
> and find it helpful to users when creating multi-language (and encoding)
> sites.
--
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]
