[ https://issues.apache.org/jira/browse/VELOCITY-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claude Brisson resolved VELOCITY-599. ------------------------------------- Resolution: Fixed I cannot guarantee for sure that the bug is fixed since I don't have access to an SQL Server instance either, but there are strong changes it is with commit 1752784, since the DataSourceResourceLoader now uses the same encoding processing as the FileResourceLoader. > DataSourceResourceLoader doesn't support UTF8 > --------------------------------------------- > > Key: VELOCITY-599 > URL: https://issues.apache.org/jira/browse/VELOCITY-599 > Project: Velocity > Issue Type: Bug > Components: Engine > Affects Versions: 1.5 > Environment: WindowsServer2003 R2, > Oracle10g(10.2.0,UTF8characterSet), jdk1.5.0_12 > Reporter: markchen > Fix For: 2.x > > > If templates are stored in the database instead of files,the characters > retrived becomes garbled. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org