I would like to contribute to the translation before the final release. What is the plan?
Hilaire
On 05.08.2009, at 14:37, Hilaire Fernandes wrote:
I would like to contribute to the translation before the final release. What is the plan?
The plan is to get all the tickets Scott mentioned reviewed, then push all changesets to the update stream, do a pre-release, upload new POTs to translate.sugarlabs.org and gather the translations (POs) for the final release.
- Bert -
2009/8/5 Bert Freudenberg bert@freudenbergs.de:
The plan is to get all the tickets Scott mentioned reviewed, then push all
I already reviewed a lot of them
changesets to the update stream, do a pre-release, upload new POTs to translate.sugarlabs.org and gather the translations (POs) for the final release.
It could be helpful to already produce a POT snapshot so translator can already review most of the translation, then another one at the timeslot of the timeline you described to fine tune the translation.
Hilaire
On 05.08.2009, at 16:17, Hilaire Fernandes wrote:
2009/8/5 Bert Freudenberg bert@freudenbergs.de:
The plan is to get all the tickets Scott mentioned reviewed, then push all
I already reviewed a lot of them
changesets to the update stream, do a pre-release, upload new POTs to translate.sugarlabs.org and gather the translations (POs) for the final release.
It could be helpful to already produce a POT snapshot so translator can already review most of the translation, then another one at the timeslot of the timeline you described to fine tune the translation.
That's exactly what I meant with "pre-release". Call it what you want, but the changesets need to be in the update stream.
- Bert -
I don't see what prevent a POT snapshot before so translators can take time to make a good translation. I don't see what make it mandatory to be linear. At least it does not work that way in free software translation I saw. Or do I miss something? In the other hand if there are only a few updated strings it does not matter to make it late.
Hilaire
2009/8/5 Bert Freudenberg bert@freudenbergs.de:
On 05.08.2009, at 16:17, Hilaire Fernandes wrote:
2009/8/5 Bert Freudenberg bert@freudenbergs.de:
The plan is to get all the tickets Scott mentioned reviewed, then push all
I already reviewed a lot of them
changesets to the update stream, do a pre-release, upload new POTs to translate.sugarlabs.org and gather the translations (POs) for the final release.
It could be helpful to already produce a POT snapshot so translator can already review most of the translation, then another one at the timeslot of the timeline you described to fine tune the translation.
That's exactly what I meant with "pre-release". Call it what you want, but the changesets need to be in the update stream.
- Bert -
etoys-dev mailing list etoys-dev@squeakland.org http://lists.squeakland.org/mailman/listinfo/etoys-dev
On 05.08.2009, at 16:41, Hilaire Fernandes wrote:
I don't see what prevent a POT snapshot before so translators can take time to make a good translation.
How do you know which strings to include if the changes have not been approved?
I don't see what make it mandatory to be linear. At least it does not work that way in free software translation I saw. Or do I miss something?
I don't know any project that does translations before the code gets merged.
In the other hand if there are only a few updated strings it does not matter to make it late.
Translations are current as of update number 2229, uploaded on July 8th, see
http://etoys.laptop.org/src/pootle.log
How current do you need it to be?
- Bert -
2009/8/5 Bert Freudenberg bert@freudenbergs.de:
On 05.08.2009, at 16:41, Hilaire Fernandes wrote:
I don't see what prevent a POT snapshot before so translators can take time to make a good translation.
How do you know which strings to include if the changes have not been approved?
Sorry, right I have been confused. I was still thinking in term of C code in CVS, where changes and .po files are all commited in the same CVS branch.
Hilaire
On Wed, Aug 5, 2009 at 11:17 PM, Hilaire Fernandeshilaire@ofset.org wrote:
It could be helpful to already produce a POT snapshot so translator can already review most of the translation, then another one at the timeslot of the timeline you described to fine tune the translation.
Hilaire, If you want to review how POT will be changed in coming release, You could easily generate POT by yourself from any image (with candidates of changes). See class comment of GetTextExporter2 about how-to.
/Korakurider
etoys-dev@lists.squeakfoundation.org