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