Spindle wizards generate spec files as following:
<?xml version="1.0" encoding="UTF-8"?>
But generated file encoding is still a container encoding
(in many cases, it is a platform default encoding, not
UTF-8). So, if I use multi-bytes chars in the spec file,
Tapestry reports ParseError in runtime.
A template variable named ${encoding} is specified as
UTF-8 at XMLFileContextType.Encoding. So I think
Spindle should set UTF-8 as a file encoding in the spec
file generation process like this:
file.setCharset("UTF-8", monitor);
Or Spindle should use a container encoding as an
${encoding} variable instead of UTF-8.
Regards.