On May 17, 2011, at 5:35 PM, pierreth wrote: > > Any other ideas? One. Now that we can have translations in gluon, it'd be nice to have global (that is, not app-specific) translation files. My thought was that the translator would look first in the current app's translations, and if it's not found, check the global translation files.
That way we could accumulate standard translation for gluon messages (and perhaps other common messages as well). Developers could override the global translations if necessary by simply supplying their own version. It's conceptually aligned with the scheme you're proposing, in the sense that it relies on primary and fallback translation files, so I think it might fit in nicely. BTW, the parametric (newish) URL router has some language selection support, but it's not hooked up: all that happens is that the language specified in the the URL ends up in the request object. That's because I wasn't using translations enough to know what the best approach would be. It'd be nice to complete that loop.
