Thank you Bert for your reply.<br><br>I've been looking at the link you posted<br><a href="https://dev.laptop.org/translate/projects/etoys/">https://dev.laptop.org/translate/projects/etoys/</a><br><br>The PO format from GNU gettext is fine, but in the etoys repositories they are not using context fields, only comments and sparsely (I've checked French, Spanish, Japanese and Russian).<br>
<br>I have some questions, maybe someone in the list can reply.<br><br>- Are there no placeholders/identifiers? no contexts? for a big project like this is looks like the context information is insufficient. You can very possibly have the same string translated in different ways depending on the context and the reverse is also true (not so much in German which tends to be very specific :) ). Well, this method of doing it with online contributions and no contexts would be very good for an application with a few pop-up menus etc, but I think it will be very difficult to keep this well managed and up to professional standards using only this information. I've downloaded a few PO files, I might be missing something.<br>
<br>- Is there some way to separate etoys from just the base image (and separated packages)? The amount of languages makes it very difficult to maintain huge monolithic tables like those, in a 1-per-language basis.<br><br>
- Is there an automatic way to extract/inject those translations from an image and see the results? looks like the OLPC people are doing it their own way and manually (possibly compiling the whole thing?), which is fine for them I guess :) but in order to have it updated and well supported in squeak base image it has to be streamlined. I think this is very, very important for the future of Squeak. Even more so if we make it to main repositories from the likes of Debian, Fedora or Ubuntu.<br>
<br>In short, I was looking for a way to translate the base image in a centralized manner, with scripts to obtain immediate results.<br><br><br><div class="gmail_quote">2008/5/27 Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>>:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On 27.05.2008, at 12:11, muyuubyou wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I haven't posted to the list in a few years but I think this is a very important topic.<br>
<br>
First of all, thanks to all developers and contributors for all the effort. The improvement in the last 2 years has been nothing short of astonishing.<br>
</blockquote>
<br></div>
Indeed :)<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
One thing that I still find lacking is squeak's internationalization support.<br>
</blockquote>
<br></div>
That improved as well, considerably so.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How is it there are no official images in other languages?<br>
</blockquote>
<br></div>
Because it's simpler to have just one image. The Etoys image uses the LocalePlugin so it can switch to the right locale on startup.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How about font packages for non-romanized alphabets? Given the amount of international involvement there should at least be a version with some sort of Unicode font (I realize that full Unicode fonts are huge). This is a show stopper for a lot of people these days.<br>
</blockquote>
<br></div>
The system supports unicode (that was the biggie in 3.8). You can use Freetype fonts now. There is experimental Pango support as well.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How is Squeak-jp working? because the Japanese kids will struggle to play with etoys in English.<br>
</blockquote>
<br></div>
It downloads a Japanese font set. Etoys in Japanese is fine.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've automated the localization of several software packages and I could give a hand with this. We need some sort of extractor-injector of text strings.<br>
</blockquote>
<br></div>
We do have that. See class GetText* classes in the OLPC Etoys image.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A propose using a CSV file in UTF-8 with the following information, for every language:<br>
</blockquote>
<br>
<br></div>
Etoys uses the gettext format which is an open-source standard:<br>
<br>
<a href="http://www.gnu.org/software/gettext/" target="_blank">http://www.gnu.org/software/gettext/</a><br>
<br>
Translation of Etoys and the base system is ongoing:<br>
<br>
<a href="https://dev.laptop.org/translate/projects/etoys/" target="_blank">https://dev.laptop.org/translate/projects/etoys/</a><br>
<br>
There are already 4312 translatable phrases, and we're adding more.<br>
<br>
This could be a nice basis for the <a href="http://squeak.org" target="_blank">squeak.org</a> version, too. It just takes somebody to grab the code.<br><font color="#888888">
<br>
- Bert -<br>
<br>
<br>
</font></blockquote></div><br>