You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by bu...@apache.org on 2003/11/18 20:31:37 UTC
DO NOT REPLY [Bug 24796] New: -
Velocity templates should be able to specify their own encoding
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24796>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24796
Velocity templates should be able to specify their own encoding
Summary: Velocity templates should be able to specify their own
encoding
Product: Velocity
Version: 1.5
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Source
AssignedTo: velocity-dev@jakarta.apache.org
ReportedBy: cmore@atg.com
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org