Nebojsa Djordjevic wrote: > 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. > If you have the countries in a data base is possible show to the user a drop list for that he chooses its country. In addition is possible filter those data by geographical region or inclusive by languages when I have finished those table. You can not make this using files. So an administrator could show in its Django project only the countries related to North America or countries with germany language only. There is a field called 'display' for this proposal.
Also is possible show to the user in the first the geographical regions and then he choose its country form that region. It's very heavy choose your country from a log list (250 countries more or less) And as the main table goes in the data base, the rest of data also because are data related to that table. In addition there are some data that could need a Many-to-many relationship as languages and countries and this is easy with the data base. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
