GinTon wrote: > Now I'm working with the languages table, and the next tables will be: > > * date format > * Currency
Well, date and currency (and IIRC number) formats are defined in LC_MONETARY, LC_NUMERIC, LC_DATE and LC_TIME on most of the *nix systems anyway. So why not using that? We already agreed to use gettext for text storage. I think that (like i18n implementation) we can use locale.py from standard python distribution as a base and work from there (current python locale implementation is not usable because is not thread safe). With that (at least for numbers, date and time) we can just copy LC_* to locale/<lang>/ dir. For start let's compile some requirements for l10n, then chose storage format and implementation. p.s. I'll post link to this thread in django-devel/user just to attract more opinions. -- Nebojša Đorđević - nesh Studio Quattro - Niš - SCG http://studioquattro.biz/ http://djnesh.blogspot.com/ | http://djnesh-django.blogspot.com/ | http://trac.studioquattro.biz/djangoutils/ Registered Linux User 282159 [http://counter.li.org] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~----------~----~----~----~------~----~------~--~---
