Some of the information that was on this page is now outdated. How-Tos exist for all the common contributor tasks, including translation, both on- and off-line, and can be found linked from Tasks and Tools.
|When editing pages that are already marked for translation, you will see section markers similar to <!--T:1-->. Usually each paragraph is one section. You should not change the markers, unless you fully delete a section, in which case you should simply remove the old marker. When adding new sections, you don't need to add marker to it – the marker will be added automatically when your changes are approved for translation. If you want to move a section, move also the section marker with it. That is the only time when you touch the markers - the system will do the rest.|
See here for more information:
2. Glossary: http://translate.sourceforge.net/wiki/guide/glossary
3. Another Glossary: http://www.glossary.com/category.php?q=Computer
UserBase proposes to have Team Leaders for each language. Techbase may, at a later date, do the same. As we get leaders appointed, they will take charge of a page of guidelines for their specific language, where they will be named. They will have final say on any question relating to their language. The guidelines will be linked from Language-specific guideline pages.
I propose that the Discussion page attached to this page should be used for orderly debate about general issues noted, particularly issues where existing markup is causing problems. I would ask you to put a Watch on Talk:Translation_Workflow.
For a fuller description of the Translate extension, read the description on the developers' website
|Monitor the status of your language statistics by monitoring the page http://userbase.kde.org//your-language-code or simply Special:LanguageStats if you have your own language set as the interface language of UserBaser.|
Volunteer Team Leaders, please link your page from here (or ask for help)