[squeak-dev] Doing spanish translation??

Hello, I'm new to this list.
I'd like to translate the official 3.10 image to spanish, and would like to know if there would be any problem to include that translation into the official image or not, just because it is a lot of work and wouldn't like to waste the time.

(I'm a native spanish speaker)

Thank you.

Hola Javier,

La imágen es mejor que se mantenga en inglés. Si lo buscas para educación, esa si está traducida al castellano.

Inscríbete en el grupo de yahoo de SqueakRos y/o ClubSmalltalk

Ahí estamos los españolitos :D

Un saludo.

P.D: Sorry for this spanis mail. Is for some appointments for he :D

On Fri, 23 May 2008 22:44:15 +0200
Javier <[hidden email]> wrote:


--
Giuseppe Luigi Punzi <[hidden email]>

On 23.05.2008, at 22:44, Javier wrote:

> Hello, I'm new to this list.
> I'd like to translate the official 3.10 image to spanish, and would  
> like to know if there would be any problem to include that  
> translation into the official image or not, just because it is a lot  
> of work and wouldn't like to waste the time.
>
> (I'm a native spanish speaker)
>
> Thank you.


Note that the LinEx guys did a nice translation of their image:

        http://dev.laptop.org/ticket/6911

which should soon be merged with the OLPC Etoys translation:

        http://dev.laptop.org/translate/projects/etoys/

(btw, Etoys now uses gettext for translating which is well supported  
and pretty much standard in the open-source world)

- Bert -

Bert Freudenberg a écrit :
Yes, it is pretty handy to have gettext support with .po file, it makes
easier to maintain translation.

Do you know about any plan to include it in Squeak image as well? Or may
be just an external gettext package ready to use will do it. Do you
think EToys team could produce such a package to test it in squeak image?
It is definitely useful to localise web application. I am wondering how
Seaside people are handling localisation. Btw, I guess Sophie people
will love to have it as well.

Hilaire

On 24.05.2008, at 08:50, Hilaire Fernandes wrote:

Maybe you could ask Korakurider if he has a complete set of patches  
(he did most of the work). Otherwise someone would have to gather the  
changesets from the etoys update stream.

> It is definitely useful to localise web application. I am wondering  
> how Seaside people are handling localisation. Btw, I guess Sophie  
> people will love to have it as well.


Maybe, yes.

- Bert -

Bert Freudenberg a écrit :

>> Do you know about any plan to include it in Squeak image as well? Or
>> may be just an external gettext package ready to use will do it. Do
>> you think EToys team could produce such a package to test it in squeak
>> image?
>
> Maybe you could ask Korakurider if he has a complete set of patches (he
> did most of the work). Otherwise someone would have to gather the
> changesets from the etoys update stream.


Korakurider, do you know of any constraint to make working your Gettext
patch for Etoys into standard Squeak.org images?

Hilaire

---------- Forwarded message ----------
From: Korakurider <[hidden email]>
Date: 2008/5/25
Subject: Re: [squeak-dev] Gettext EToys patches for Squeak.org
To: [hidden email]


Hilaire, I am replying to you as I 'm not a subscriber of squeak-dev.
Please feel free to forward this.

On Sat, May 24, 2008 at 7:28 PM, Hilaire Fernandes <[hidden email]> wrote:
> Korakurider, do you know of any constraint to make working your Gettext
> patch for Etoys into standard Squeak.org images?
 Constraint of what ?

 About my patches, someone needs to pull complete changes from the
stream; some changeset pushed actually were revised from my original
and Takashi wrote some.  And I don't keep complete set.

 Here are some thought:
 + Gettext based translation ecosystem consists of several effort.
   Your scope and goal need to be planned before start the work.
   -- translation engine based on gettext emulation and refactoring
to existing translation engine
   -- small facility to manage translation domain
   -- POT extractor
   -- massive changes to apply #translatedNoop to code so that all
strings to translate will be extracted to POT
   -- translation portal and central repository where community work on

 + how to define translation domain is important and difficult.  I
think even for OLPC etoys we haven't gotten good scheme.

/Korakurider



--
http://blog.ofset.org/hilaire