<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.1">
</HEAD>
<BODY>
Hello,<BR>
<BR>
I have done a partial clean, now:<BR>
6250 strings (50 without translation yet)<BR>
<BR>
I can translate this 50 ones but I don't know how in a hurry we are, all of us have a lot of job.<BR>
<BR>
Regards<BR>
<BR>
El mar, 03-06-2008 a las 09:59 +0200, José Luis Redrejo escribió:<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">2008/6/2 Yoshiki Ohshima <<A HREF="mailto:yoshiki@vpri.org">yoshiki@vpri.org</A>>:</FONT><BR>
<BLOCKQUOTE>
<FONT COLOR="#000000"> Hello,</FONT><BR>
<BR>
<FONT COLOR="#000000"> We are still trying to package the Etoys for non-XO environments,</FONT><BR>
<FONT COLOR="#000000">along with, of course, for XO.</FONT><BR>
<BR>
<FONT COLOR="#000000"> Currently, end of June is the *real* target of release day of non-XO</FONT><BR>
<FONT COLOR="#000000">packages. The idea is to put relatively small set of languages in it,</FONT><BR>
<FONT COLOR="#000000">and it looks like English, German and French are most complete ones.</FONT><BR>
<FONT COLOR="#000000">(Thank you!)</FONT><BR>
<BR>
<FONT COLOR="#000000"> But, for the US audience, (new world's) Spanish is also important.</FONT><BR>
<FONT COLOR="#000000">And Portugese (br and pt) seems to be fairly good to me, but of course</FONT><BR>
<FONT COLOR="#000000">I can't tell the quality right away.</FONT><BR>
<BR>
<FONT COLOR="#000000"> Can you help us giving the information of the translation quality</FONT><BR>
<FONT COLOR="#000000">and completeness for these languages? For the non-XO environment, we</FONT><BR>
<FONT COLOR="#000000">will not have good font rendering mechanism other than what we have</FONT><BR>
<FONT COLOR="#000000">now, so still the main target is the Latin languages.</FONT><BR>
<BR>
<FONT COLOR="#000000"> The completeness doesn't have to be so close to 100%, as now many of</FONT><BR>
<FONT COLOR="#000000">the phrases are not for Etoys (rather for the Smalltalk development).</FONT><BR>
<FONT COLOR="#000000">But we would like to hear the opinions of the native speakers.</FONT><BR>
<BR>
<FONT COLOR="#000000"> Please visit</FONT><BR>
<BR>
<FONT COLOR="#000000"><A HREF="https://dev.laptop.org/translate/">https://dev.laptop.org/translate/</A></FONT><BR>
<BR>
<FONT COLOR="#000000">and see how far the translation are going in terms of quality and</FONT><BR>
<FONT COLOR="#000000">coverages. Bert told us that there is an old style .translation file</FONT><BR>
<FONT COLOR="#000000">for Spanish. We can convert it to .po file, but not sure again if we</FONT><BR>
<FONT COLOR="#000000">should merge them to the site, as it might wipe out newly translated</FONT><BR>
<FONT COLOR="#000000">phrases. Does anybody has good ideas how to proceed?</FONT>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<FONT COLOR="#000000">Yoshiki, as you know, in LinEx we have all the strings translated for the etoys image (plus some other strings from some packages as drgeo, skeleton, etc.). Antonio Moreno has contacted with some of the etoys people, but the answers are not really clear about the way you want us to give you the translation. Our current image is totally based on the current olpc image , with changesets added from us, but we have all the classes and objects the etoys image has, so if you give the exact way you want us to extract the translation you can have the spanish translation finished (and tested & checked) right now.</FONT><BR>
<FONT COLOR="#000000">About the newly translated phrases, if our image has been used and tested for several years, with teachers fixing translations when some mistake was found, what's the problem on wiping out newly translated phrases that has not been checked for so many people?</FONT><BR>
<BR>
<FONT COLOR="#000000">Regards.</FONT><BR>
<FONT COLOR="#000000">José L.</FONT><BR>
<BR>
</BLOCKQUOTE>
</BODY>
</HTML>