[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Localising user-supplied scripts
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2009-04-30 21:57:19
Message-ID: 200904302357.21468.aacid () kde ! org
[Download RAW message or body]

A Dijous, 30 d'abril de 2009, Andrew Coles va escriure:
> > AFAIK that has never been done, what's your idea for shipping the
> > translations? Doing it inside the script itself?
>
> That I'm not sure on, and I don't even have any particular ideas - it's
> related to the untranslated strings in amarok, which stem from scripts that
> ship with it.  They're after supporting script localisation in a future
> release, so I was wondering if such a thing had been done anywhere - and if
> so, was going to look at porting it to amarok to take some load off the
> developers.
>
> If I was pressed into coming up with some ideas, I'd think along the lines
> of a resource bundle attached to a script containing the translations (and
> other things the script needs).  Then, when the script is loaded, set up an
> i18n backend using the relevant translation from the resource bundle, and
> send i18n calls from the script through this.  I don't know the i18n
> backend as well as perhaps I might, though, so I'd not be keen on taking up
> the idea of doing that from scratch.

I think Chusslove is the only one that can evaluate how crazy^Wdoable that 
idea is.

Chusslove?

Albert

>
> Best,
>
> Andrew


[prev in list] [next in list] [prev in thread] [next in thread]