I had a similar problem. I am using tap4.0.2 but maybe this helps. I think you
should try to specify the submit as an explicit component in the .page with the
value as a component binding, like the following example:
component id=MySubmit type=Submit
binding name=value
That probably helps you if you are declaring the .page encoding to be UTF-8.
I.e.
?xml version=1.0 encoding=UTF-8?
But you can set the encoding for templates globally by setting a property in
the .application file (and also locally for libraries, pages etc) with:
property
You can't do that if you want localization, though. Really, the best
way to solve this is to just use a multi-byte character encoding to
put messages in the .properties file. That means writing them so that
they look correct when viewed with a multi-byte capable text editor.
Assuming that
