Neboja Ðordevic wrote: > On 28 Jul 2006, at 13:48, GinTon wrote: > > With LC_* (or maybe some of L10N XML based formats <ducks>) approach > *all* of the django projects will be using the *same* files - no need > to update all of the django projects when new locale is added. And When the tables are finished it is not necessary add any more so it is not necessary update the Django projects. Anyway this is not any problem because until version 1.0 could suffer changes significatives.
> LC_* approach *is* standard (at least on POSIX systems) for storing > this type of information (number, currency, date and time), see > http://www.opengroup.org/onlinepubs/007908799/xbd/locale.html. > For the same reason django uses .po files instead database based > translations. LC_* approach is a standard *for operating systems based on Unix*. It is not a stardard for a framework based on a data base. > > I already have created tables about countries, languages, countries & > > languages, subdivisions, and time zones. With all those data there are > > many possibilities in order to make the easiest life to the > > administrators and the own users. > > And I don't need this. I say you what I already made it until now. > And for above, what exactly are advantages for database based > approach (except for caching exchange rates for the money filter)? As > I already said, I'm talking about a *core* L10N functionality. I say you the disadvantages about use LC*: 1) You need all locales installed in your system to let the correct localization to users of whatever country. 2) This system is more slow that use directly the data base: You have to use a tool to get data from a directories and files, and it will be more slow when you have s system with a lot of users with different locales. If you think that using directories and files is more fast that using a data base then I don't know why you are using a framework based on a 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 -~----------~----~----~----~------~----~------~--~---
