[OpenLayers-Dev] status of translation possibilities

Jachym Cepicky jachym.cepicky at gmail.com
Fri Oct 19 09:08:35 EDT 2007


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.

Jachym

> > Anyway, to quote myself on interpolation ;-) :
> 
> Right, I remembered this message. Per the OpenLayers commit policy, we
> prefer (unless absolutely neccesary) to get a CLA for submissions from
> their author, so they can be released under ClearBSD. (Understaning the
> legal implications of LGPL is way more than I have the legal brain cells
> for.) I assume that's not really a problem, but I'm mentioniong it
> anyway :) I'll come back to it when we get that far in the code.
> 
> Regards,
-- 
Jachym Cepicky
e-mail: jachym.cepicky at gmail.com
URL: http://les-ejk.cz
GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?=
	=?ISO-8859-1?Q?_zpr=E1vy?=
Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20071019/dd423f2a/attachment.bin


More information about the Dev mailing list