![]() For local translations its not a problem to define a separate role with limited access to te language system. May be some people in a translation group have the overview and can see the consequences. If we use in different cultures different wordings for such things we can't translate it in different ways. Mostly it is used as 'introduction', in assignments it is a 'task'. ![]() A good exmaple is the 'description' string in activities. Often user have ideas to cahnge something and dodn't know that strings often are used in different contexts. Its not a good idea to do this directly in the local language version of the school. I red and understood the idea of branches for translations and this is a good idea.Ī whole school submitting new translations is a interesting idea but we have engouh instruments to do this in courses. every site administrator may choose which version (clone) they want to use.language ZIP packs are generated auto-magically from all repositories available.the maintainer can decide to pull changes from other repositories, compare them against their own etc.anybody can decide to create their own fork (clone) of the official language pack repository and start making modifications, changes etc.They keep branches for all stable releases. every language pack is maintained by a single "official" translator.But it also fits our needs and process much better. Not only branching and merging is much easier in GIT than in CVS. Let me be brave and propose using GIT instead of CVS for language packs (what? is David crazy?). I am little bit afraid of terminology wars, mentioned by Koen. Code maintaining is about communication, not permission. IMHO every language pack needs a maintainer (Pythonists use term BDFL) who makes decisions. How would we get English files from several branches into a single installation?Īd collaborative translation: to be honest, I am very sceptical here. How? The translation is done against the English pack at a given branch. How many translators use CVS at the moment?Įloy noted that the translation tool itself should support branches. is needed but after several successful commits this might become an easy daily task. More documentation, step-by-step tutorials etc. I think we will have to help our translators to use CVS branching features. I would really love to see language packages being branched. But we know this leads to a lot of obsoleted strings and helpfiles. ![]() foobar2.html instead of current foobar.html) instead of changing the current ones so the backward compatibility is preserved. The current correct way is to introduce new helpfiles (eg. Helen has mentioned some issues with the help files for the new gradebook. Sorry for this long post - with this length it hardly looks like a summary Maybe those last two groups can have a CVS account to do their thing on the files, but I would keep that as an exception. translators who like translating directly on the files. : yet another set of installations to maintain no need to change anything on the translation interface no need to install anything for translators: translating is done on the Moodle servers no need to do anything with CVS for translators - branching is automatically The box updates dailyĪ robot can daily move the translated files in the correct CVS branch. ![]() A demo course can be stored (and may be restored every X time) to have something to play with. We could make a clean start for Moodle 2.0 on a new download page, like we did for 1.6, but then the problem starts building up if we don't do branching.Īnother track is to install on a box all maintained Moodle versions, give translators an admin account on it with the translating capability set. 3) lang download (both from web page and from within moodle must know about branches)īranching involves having a Moodle 1.9, a Moodle 2.0, Moodle 2.1 and perform each translation in the corresponding one and committing the translation to the corresponding branch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |