The only relevant technical point here is "Inheritance". If
Component A
inherits Component B, then the properties would have to be repeated
in the
property file corresponding to the inherited Component as i don't
think
properties follow inheritance rules (imo).
Component B "inherits" the
live anyway!
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Best-practice-on-i18n-tp3245918p3246828.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> -
>
s; like ease of maintenance etc. for clients.
thanks
-
Don't take life too seriously, your'e not getting out it alive anyway!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Best-practice-on-i18n-tp3245918p3246828.html
Sent from the Users forum mailing l
1 10:03 AM
To: users@wicket.apache.org
Subject: Best practice on i18n
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? F.e. my form component needs i18n, so does my page which
holds
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,
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? F.e. my form component needs i18n, so does my page which
holds the form alone. Wicket does of course not search in the i18n
files for the pag
