Confirmed users
135
edits
L10n:Teams:nl: Difference between revisions
Jump to navigation
Jump to search
→L10n kit
| Line 111: | Line 111: | ||
====L10n kit==== | ====L10n kit==== | ||
;Tools: | ;Tools: | ||
We use the Mercurial version control system (Hg) to manage our source code and localizations. Localizers in training can get a updated zipfile with the localization files or pull the files from [https://developer.mozilla.org/en-US/docs/Localizing_with_Mercurial?redirectlocale=en-US&redirectslug=L10n_on_Mercurial Mercurial] | |||
All localizers working on software projects use a texteditor. The localization process is managed individually by each module owner on his own schedule. When possible web content is managed on [https://localize.mozilla.org/nl/ Verbatim], in order to let more people cooperate. | All localizers working on software projects use a texteditor. The localization process is managed individually by each module owner on his own schedule. When possible web content is managed on [https://localize.mozilla.org/nl/ Verbatim], in order to let more people cooperate. | ||
;Translation Memory: | ;Translation Memory: | ||
We currently use [http://transvision.mozfr.org/ Transvision]. This tool is useful in several situations, for example to check if wrong strings belong to the software or an add-on, identify in which file a particular string is saved or check how an English string is localized (this is extremely important for SUMO articles). | We currently use [http://transvision.mozfr.org/ Transvision]. This tool is useful in several situations, for example to check if wrong strings belong to the software or an add-on, identify in which file a particular string is saved or check how an English string is localized (this is extremely important for SUMO articles). | ||