You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/10/15 07:36:00 UTC

[jira] [Commented] (VELOCITY-229) Velocity templates should be able to specify their own encoding

    [ https://issues.apache.org/jira/browse/VELOCITY-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649847#comment-16649847 ] 

Michael Osipov commented on VELOCITY-229:
-----------------------------------------

Fully agree with Claude, we shouldn't fiddle with a pushback reader like XML adding unnecessary complexity.

> 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: ASF.LICENSE.NOT.GRANTED--Template.diff, ASF.LICENSE.NOT.GRANTED--encoding-support.jar
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org