Re: locales, lang menu and usages

Hi

<snip>

> As in java Locale http://jan.netcomp.monash.edu.au/i18n/locale/locale.html
> I think that i18N and Locale classes should be used as a 'locale 
> server', but keep lang and country as independant values.

I completely agree.

> Proposed changes

<snip>

I agree with most things, but I'd go a step further:

  * The locale state should be handled by i18n, or possibly a class in 
i18n. Not in Client.
  * We should allow for overriding all values connected to a locale. 
This should look like KDE's/Windows' locale selection dialog: Select a 
locale to get defaults for and tweak stuff. This should also be stored 
in Client. If you want to store this in a DB and connect to a user 
account, this does not belong into Client, User or I18n, but rather in a 
user_management module in vortex.

*m


-- 
GPG key: http://www.ggnore.net/~mholtgrewe/personal/files/public_key.asc
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev