I think you've hit the nail on the head and that this relates to TAP5-1778.
As a work around, can you put your special chars in a language specific properties file? By default, prop files are treated as UTF-8. You can also override the PropertiesFileParser if you need. Another option is to override the TemplateParser service to use UTF-8. See the patch attached to the issue.
