Hi,

I noticed that, too, and also I don't like that every time a string is
looked up the server will also check whether the string needs to be
added... if you changed the string, it's added as new and the old
string's translations won't be accessible anymore but they'll still
clog up the database... I will soon be presenting a more efficient
solution.
Basic improvements:
- use of IDs for faster lookup of view translations; these IDs will
also make sure that updated strings are not lost; rather the
translation interface will present the new string with the old
translation for updating
- no looking-up of base-language translations except if it's a symbol
- updating or adding of strings will happen only on request and you
can set it to run every time you deploy, weekly or whatever interval
you think is good
- support for multiple variables in one string
- no need to change the application code compared to how it looks with
standard Globalize

Best wishes,

Judith



On Sun, May 25, 2008 at 11:59 PM, Nicola Piccinini <piccinini@...> wrote: