![]() Remove your unknown.*-file, to start collecting new keys from scratch.Send us a pull request, again with mappings_unknown updated: prefix.Prefix your commit message by mappings_unknown updated:.Review your changes to mappings_unknown for possible sensitive information, like server names, and replace by 'XXX'.Update mappings_unknown from unknown.*:.Pull the latest changes, to be sure you have the latest version of mappings_unknown.From time to time, check the unknown.* file and send us a pull request:.keys for which there is no matching entry in the master mapping file yet note that unknown.* is an ignored file which is 'owned' by you SmartGit will now have created several new files in the specified developmentdirectory, most importantly unknown.* which contains not yet known keys, i.e.=C\:/temp/smartgit-translations.git/mapping =C\:/temp/smartgit-translations.git/zh-CN Locate smartgit.properties in SmartGit's settings directory (see About dialog) and add following lines there:.Make sure SmartGit is not running (Repository|Exit).For example:ĭue to the dynamic generation of SmartGit texts, the master mapping does not contain all keys, but only all currently known keys which have been 'collected' by our contributors and us. If the translation of a specific text should remain identical to the original English text, prefix the text by =. Note! Please make sure that your pull request does not contain any unrelated formatting changes (like line endings) or any other unnecessary changes, like re-orderings (keys are automatically sorted by us). Send us a pull request, again with Chinese translation update: prefix.Prefix your commit message by Chinese translation updated:.Perform the translation in mapping_dev.*, i.e.Use mapping_todo_new.* to determine which text you want to translate.Check for pending pull requests, to see which translations are currently in progress.Follow the preparations, as explained above.Help to translateĪll keys in mapping_todo_new.* need translation and every single new translation is welcome! Note! Please only send pull requests for one of these two versions. contains translations for the corresponding SmartGit version master contains translations for the current Preview version.Be sure to use the latest released or the current preview version of SmartGit.In either case, you have to fork and clone this repository and ensure that you are in the correct branch: Help to collect: collect not yet known keys to populate the master mapping.Help to translate: translate not yet translated texts from mapping_todo_new.* language mappings.You can contribute to the localization of SmartGit in two ways: mapping_dev.* will be updated by contributers and synchronized back by us to SmartGit sources.įor every SmartGit version, there is a separate branch, like smartgit-20.2. The master mapping will be updated by us from SmartGit sources in regular intervals. mapping_todo_new.* contains only not yet translated texts (with their original English text) this file is auto-generated and only present to make looking up missing translations easier. ![]() mapping_dev.* contains translations for all keys (not yet translated texts will show up in English).For all currently supported locales, corresponding sub-directories contain mapping files with appropriate translations: The root mapping file ('master mapping') contains all currently known keys with their original, English texts. The main UI components have keys assigned which are used to look up translations from mapping files. Many of these strings are dynamically composed. SmartGit contains the various UI texts ('strings') directly in the source code. This repository contains translation files for the Git client SmartGit: SmartGit Localization - SmartGit Translation Files
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |