David Hello
I'm still confused:
1) I cant translate moodle 1.9.x strings as I used to with cvs tortoiseCVS anymore (don't kbnow why).
Can I do that in AMOS? I can see there is 1.9 (checkbox) -when I checked it only, and the strings that I want to fix\add\commit are in a white background. Anyway I changed the translation\added and clicked on stage but I can't commit as I can do in 2.1 strings.
Where am I wrong? how can I update\fix\add strings of 1.9 version through AMOS?
2) Another question: we are translating moodle 2.1 but never touched The 2.2 (beta). When 2.2 will be the formal lang and no more beta, Will all the 2.1 strings automaticly be propogate to 2.2 or do we need to do something?
Thanks a lot!
re 1 - that's weird. I just checked and I am still able to commit 1.x translations to CVS normally. You may want to discuss this issue with Koen to find out what's going on (does your CVS client complain about anything particular? Permissions or so?).
And no, you can't use AMOS for translating 1.9 packages. It has never been planned to support that. AMOS tracks changes in CVS in read-only mode so that you can see 1.9 strings for reference but noone can commit changes to 1.9 branch in AMOS. And one day, when Moodle HQ stops supporting Moodle 1.9, that branch may be dropped from AMOS repository completely.
re 2 - You can use AMOS Merge tool at the Stage page exactly for that. No automatic step will be done for it. You have to merge strings from 2.1 to 2.2 manually. See also the Propagate feature that actually minimises the need of the merge. Both these features should be described at the AMOS docs page.
And no, you can't use AMOS for translating 1.9 packages. It has never been planned to support that. AMOS tracks changes in CVS in read-only mode so that you can see 1.9 strings for reference but noone can commit changes to 1.9 branch in AMOS. And one day, when Moodle HQ stops supporting Moodle 1.9, that branch may be dropped from AMOS repository completely.
re 2 - You can use AMOS Merge tool at the Stage page exactly for that. No automatic step will be done for it. You have to merge strings from 2.1 to 2.2 manually. See also the Propagate feature that actually minimises the need of the merge. Both these features should be described at the AMOS docs page.
Hey
Thanks for the replies.
1 ) Now it's ok I mange to figure it out
2) Now I see that the default of translations in tick with 2.2 and not 2.1
If I'm translating 2.2 strings and committing them, and I want them to be in 2.1 too. Do I need to propagate them back to 2.1? only by clicking on the propagate button ??
Thanks
Yes, use the propagate button before you commit staged 2.2 translations. You will see that the stage grows so that the strings will be committed to 2.2, 2.1 and even 2.0 as necessary.
The merge tool at the empty stage page can be used from time to time to detect and fix eventual missed propagations.
I hope other translators would join to this thread and try to explain it in their words - I often realized it helps
Yes, actually this explanation helped me to understand
thanks you