On Wed, Mar 17, 2010 at 05:15:49PM -0400, Suresh Chandrasekharan wrote:
> If requirements exist, we can look into how to provide C bindings
> for this python library later.

Who sets requirements?  I only know that there are definitely uses for C
bindings of this API in ONNV and elsewhere.

> The following functions in the library do support RFC3066 language tags

Sorry, I typoed, it's RFC5646.

>    def g11nsvc_get_all_system_locales(self, lang_code=None): -->
> returns all locales for lang_code
>    def g11nsvc_get_all_system_utf8_locales(self, lang_code=None):
> --> Returns UTF-8 locales for lang_code
>    def g11nsvc_get_all_system_legacy_locales(self, lang_code=None):
> --> Returns non-UTF-8 locales for lang code
>    def g11nsvc_get_localename_from_timezone(self, timezone,
> lang_code, check_locale=True, encoding="UTF-8"): --> Contructs a
> locale from a timezone/lang code info

Ah, that was unclear to me.  Do make sure that the documents state this
explicitly.  (RFC5646 language tags are not always equivalent to the
ISO-639 language codes.  There's not always a direct mapping of RFC5646
language tag + codeset to locale.  Matching rules are specified in RFC
4647.)

Nico
-- 

Reply via email to