THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Individual pages and components can override the values defined in the message catalog.Wiki Markup
| Warning | ||
|---|---|---|
| ||
Make sure that your properties files don't contain byte order marks (BOM), because Java – and thus Tapestry – doesn'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. |
{note} {float}
Properties File Charset
Tapestry uses the UTF-8 character set (charset) when reading the properties files in a message catalog. This means that you don't have to use the Java native2ascii tool.
...
If you change a property file in a message catalog, you'll see the change immediately, just as with component classes and component templates (provided you're not running in production mode).
Asset Localization
When injecting assets, the injected asset will be localized as well. A search for the closest match for the active locale is made, and the final Asset will reflect that.
...
en (English) | el (Greek) | it (Italian) | pl (Polish) | sv (Swedish) |
bg (Bulgarian) | es (Spanish) | ja (Japanese) | pt (Portuguese) | vi (Vietnamese) |
cs (Czech)1 | fi (Finnish) | mk (Macedonian) | ru (Russian) | zh (Chinese) |
da (Danish) | fr (French) | nl (Dutch) | sl (Slovenian)2 |
|
de (German) | hr (Croatian) | no (Norwegian) | sr (Serbian) |
|
1 as of Tapestry 5.3.8
2 as of Tapestry 5.4
Providing translations for Tapestry built-in messages
...
| Info |
|---|
Please note that a patch is always preferred over an archive of properties files. |
| Scrollbar |
|---|