...
Tapestry uses the UTF-8
charset when reading the properties files in a message catalog. This means that you don't have to use the Java native2ascii
tool. Make sure that your properties files don't contain byte order marks (BOM) as Java - and thus Tapestry - dondoesn't support BOM in properties files (see http://bugs.sun.com/view_bug.do?bug_id=4508058). Some editors write them out when saving a file in UTF-8, so watch out.
...
Messages can be accessed in one of two ways:
- Using the "message:" binding prefixexpression in a component template
- By injecting the component's Messages object
In the first case, you may use the message: binding prefix with component parameters, or with template expansions:
...