On 23 oct. 07, at 16:00, Bert Freudenberg wrote:
Per-package translation files can provide translations for a specific class category. This overrides the default translation file provided with the system. We are testing this with DrGeoII in fact, we made a DrGeoII.mo file and place that next to the etoys.mo file containing the system translations, and translations from the new file will get picked up for all classes in the DrGeoII-* categories.
Ok I would have to really have a look to understand. With hilaire we always wanted to have translations attached to packages.
This work is not finished and integrated yet, but supporting independent translations for add-on packages has been a design requirement from the beginning, since we do want to support those additions as well as possible.
To get features like this into the squeak.org version, someone would have to take on the task of "harvesting" interesting things from the OLPC etoys update stream.
yes I would like to do this task if I participate to the 3.11 Now I was wondering how I could keep tracks of this (besides reading the changesets)
- Bert -
On Oct 23, 2007, at 7:35 , stephane ducasse wrote:
Bert
How do you store the translations? Because it would be cool to get them per packages as ressources package. I know that OLPC does not have mc but it would be good for Squeak.
I would like to see a merge or flow from OLPC new features to Squeak. What would be the process to make sure that nothing is lost for squeak?
Stef
Actually, we do not use NLT anymore for OLPC. We exported all translations to po files:
https://translations.launchpad.net/etoys/first-deployment/+pots/ etoys
This lets use use the "gettext" translation tools that are the standard in Linux.
It is very easy to add languages, merge, etc, but I do not find how to delete one of them.
Another question: Which is Babel function?
Not sure what the question is.
- Bert -