Hi,
After some trying we found a good practice is:
- Self contained independant components have their own resource file
- a page has its own file which also contains the keys for the panels
on that page (as long as those panels are not being reused on other
pages and are in the same package, otherwise those panels are treated
as components)
- common strings like save, cancel are stored in a resource file with
the base page
Cheers
Hans
Am 29.01.2011 um 09:03 schrieb Christian Grobmeier
<[email protected]>:
Hello,
I have read and understand about i18n but I am curious about best
practices.
Is it really a good option to have several language files per
component?
<snip...>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]