I agree that only the original text should be stored in the database. The idea behind this change is to be a possible step on the road to allow this to happen. Habari already stores data in the db in the language to which it set at installation.
See r3714 (http://trac.habariproject.org/habari/changeset/3714) for an instance of where the function allows strings to be properly translated, yet used in their english form for internal consistency. If there is a better, or easier way to do this, I would welcome seeing it. As regards different users and different languages, at the moment all users use the same locale. Whatever is set at installation, or on the options page, is the language all users will see in Habari's admin interface (with the exception of strings that aren't properly translated as yet). Rick On Sep 9, 12:39 pm, Guido Erlinger <[email protected]> wrote: > Hello, > > My thougths to changeset #3711 > ==>http://trac.habariproject.org/habari/changeset/3711 > > I think this is not a good idea, because it just will work if ONLY > ONE locale languge is used. > > If I install habari with german language, german translations will > be stored in database! If there is another user, who uses for > instance french language, _u() will not find the german locale in > the french catalog ... this means the original english text will not > be found. > > In my opinion: If there is the need to store localizable texts in > the database, it should be english! > > cu, helpy --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
