[OpenLayers-Dev] status of translation possibilities

Christopher Schmidt crschmidt at metacarta.com
Fri Oct 19 10:18:27 EDT 2007

On Fri, Oct 19, 2007 at 03:08:35PM +0200, Jachym Cepicky wrote:
> Hi
> Christopher Schmidt p????e v P?? 19. 10. 2007 v 07:47 -0400:
> > On Fri, Oct 19, 2007 at 01:05:18PM +0200, Gertjan van Oosten wrote:
> > > Note that even when you have i18n texts, you still need to take into
> > > account that the developer adding new strings to the code and the people
> > > doing the translation thereof into the other supported languages are
> > > generally not the same.  Which means you need some sort of fall-back
> > > mechanism for message keys that remain as yet untranslated.  In
> > > MapBuilder the fall back is on the default language "en".
> > 
> > Good point. I had forgotten about that. We should update teh RFC to take
> > that (and other things in this thread) into account.
> > 
> I was thinking, that rather then return default "en" translation, it
> could return the untranslated message back. Since  I still suppose,
> translation keys will be strings in english, result will be the same.

Right. Though perhaps support for a 'fallback' language in addition to
just returning the translation string makes sense? It wouldn't be that
hard, in any case -- a couple extra lines of code in String.translate() 

Christopher Schmidt

More information about the Dev mailing list