Hi Pierre,
this is imho the job of a specific LocaleProvider implementation.
Your proposition could be a good fit for the DefaultLocaleProvider
implementation. (if you know of a better name, that would be cool)
Best regards,
Geert
On 2-dec-05, at 12:58, Raoul Pierre wrote:
Geert,
OK to be always able to get all the locales specified by any
origine (template, element, site, participent, client,
others?).The issue here is to define rules for the order of
priority between the locale in accordance with theirs origines.
This is defined here, in the same way as the rules for properties:
http://rifers.org/wiki/display/RIFE/IoC+properties+support+inside
+the +repository
Proposition:
1/ Each element builds its own list (LocaleProvider) of Locale
from, by decreasing order of priority:
- a "required" locale, specified by new L10N_REQUIRED_LANGUAGE/
COUNTRY properties
- a "user" locale, specified by a global variable
- a "request" list, created from the Accept-Language HTTP
request header
- a "default" locale, specified by L10N_DEFAULT_LANGUAGE/COUNTRY
properties
2/ each level may be available or not
3/ We keep the usual rules for priority of properties themselve
(see IoC properties support inside the repository)
Regards
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
