Hi,
>> really happy to use it - but we could just switch the storage of
>> translations to storage under Locale names, in t hat case it would
>> just
>> directly work through the magic of gettext.find. The storage would
>> look
>> like this:
>> locale/pt_BR/LC_MESSAGES/django.po
>> locale/de/LC_M
On 12-10-2005, at 8:32, hugo wrote:
Actually no, I am _first_ checking for the full language spec, only if
that fails I am checking for a base language spec. That's needed,
because people might just send a accept-language for de-de, but there
isn't a de-de language available, only a de language
>In Changeset 841 you are stripping anything after a '-'. This would
>make a huge problem for translation based on language sub-tag. OTOH
>you can use _expand_lang from gettext to retrieve *list* of
>normalized language names for requested locale. You only must replace
>'-' with '_' before calling
to hugo:
In Changeset 841 you are stripping anything after a '-'. This would
make a huge problem for translation based on language sub-tag. OTOH
you can use _expand_lang from gettext to retrieve *list* of
normalized language names for requested locale. You only must replace
'-' with '_'
