GinTon wrote:
> 
> Nebojsa Djordjevic wrote:
>> GinTon wrote:
>>> With that, there are 2 problems:
>>>
>>> 1) Django could be running into a system different from *unix as
>>> Windows, and I don't know if MacOs have those definitions (I'm supposed
>>> that yes, because is *unix).
>> It's like that we use now with gettext. We *will* replicate LC_* files in 
>> the django/conf/locale/<lang>/ dir for
>> supported locales so windows users will not be left out.
>>
> replicate LC_* files?
> 
> Uff! I see this very dirty. I think that is best use a data base
> related a countries table that have been already created.
> 

Why database? LC_* replication is only for users which will not have LC_* stuff 
and to allow translators to work on
them. Also, we can reuse most of standard locale.py if we choose LC approach.

For me it even dirtier that I'll have <locale tables> * <django project> 
installed instead of replicating (approx 30)
LC_* files inside django/conf/locale.

Localization data will not be changed often so let's make it accessible to all 
installed django projects without need
for per project installation.

IMHO static data (like base translations, l10n stuff, countries, ...) should be 
stored into files not in the database.

> So when a user chooses where is from, the application can show him data
> about its local date, time, etc and whatever data related to its
> country.

Just add call to (IIRC) django.utils.set_locale(locale) after selection (if 
user wants that - for example I often select
my country and I'll still wish to see content in the English (ie. translation 
sucks ;) ) ).

-- 
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to