Difference between revisions of "Development:Translations:FrenchWorkTree"
Greendreamer (talk | contribs) m (Added a language bar) |
Greendreamer (talk | contribs) (translated in english) |
||
| Line 1: | Line 1: | ||
{{Languages|En|Development:Translations:FrenchWorkTree}} | {{Languages|En|Development:Translations:FrenchWorkTree}} | ||
| − | = | + | = Creation = |
| − | + | A new repository has been created on github https://github.com/costalfy/Vega-Strike. It holds in the sourceforge's trunk's data folder dated 13/04/2014 (r13675). | |
| − | + | ||
| + | I had to delete following files in order to not exceed my quota. | ||
* *.bmp | * *.bmp | ||
* *.psd | * *.psd | ||
| Line 14: | Line 15: | ||
* /textures | * /textures | ||
| − | + | I've created a new folder i18n/LC_MESSAGES, which will contain files to traduce<br/> | |
| + | Some indications for the Github repository use are proposed here: [[Development:Translation:FrenchWorkTree:Github |Github]] | ||
| + | |||
| + | = Process = | ||
| + | Please read carefully the doc about [[Development:Translation:FrenchWorkTree:Github|how to work with github]] and [[Development:Translations:FrenchWorkTree:Notes|comments on what must be translated]] in the source code. | ||
| + | == Add gettext tags in the source code == | ||
| + | Adding internationalization in python or c++ code is fairly simple. | ||
| + | You have to scan the source code, and spot the hardcoded english text. Then, for each text, you have to coat it in a gettext tag '''_(...)''' like this : | ||
| + | |||
| + | Base.Message("No? Come back to me again if you change your mind.") | ||
| + | becomes : | ||
| + | Base.Message(_("No? Come back to me again if you change your mind.")) | ||
| + | |||
| + | Some exemples are already on the repository https://github.com/costalfy/Vega-Strike/commit/9cf2078c3fc39681404e59512b2a86503b49f887 | ||
| + | |||
| + | [[Development:Translations:FrenchWorkTree:Notes | Notes on translatable texts in diffrent files formats]] | ||
| + | |||
| + | == Generate the .po file from the source code, with PoEdit == | ||
| + | When all the source code will have been scanned, we'll use this software [http://www.poedit.net/ PoEdit], to scan the source code and locate all added tags : _(...). | ||
| + | The software will create the vegastrike-fr_FR.po file, which will contain all translatable texts... magic :) | ||
| + | |||
| + | == Translate the .po with PoEdit == | ||
| + | Translators will use the same software to open the /data/i18n/LC_MESSAGES/vegastrike-fr_FR.po file, and will have to translate each line... This is less magic ;-) | ||
| + | |||
| + | = Progress = | ||
| + | Please add here the tree which has been processed. If an entire folder is processed, please don't show all files list, a (*) near the folder name will be enough ;-) | ||
| + | data | ||
| + | |---bases (*) (green) | ||
| + | | |---fixers (*) (Obu) | ||
| + | | |---communications (en cours) (Obu) | ||
| + | |---mission (*) I had to re-factor all the .mission for poedit to detect translatable text (costalfy) | ||
| + | |---modules (*) (green) | ||
| + | | |-------- quests (*) ( ezee ) | ||
Revision as of 22:22, 19 May 2014
View this site in other languages: Deutsch – English – Français – Español – Polski – Italiano – Nederlands – Руccкий – 简体中文
Contents
Creation
A new repository has been created on github https://github.com/costalfy/Vega-Strike. It holds in the sourceforge's trunk's data folder dated 13/04/2014 (r13675).
I had to delete following files in order to not exceed my quota.
- *.bmp
- *.psd
- *.jpg
- *.png
- *.ogg
- *.texture
- *.image
- *.bfxm
- /textures
I've created a new folder i18n/LC_MESSAGES, which will contain files to traduce
Some indications for the Github repository use are proposed here: Github
Process
Please read carefully the doc about how to work with github and comments on what must be translated in the source code.
Add gettext tags in the source code
Adding internationalization in python or c++ code is fairly simple. You have to scan the source code, and spot the hardcoded english text. Then, for each text, you have to coat it in a gettext tag _(...) like this :
Base.Message("No? Come back to me again if you change your mind.")
becomes :
Base.Message(_("No? Come back to me again if you change your mind."))
Some exemples are already on the repository https://github.com/costalfy/Vega-Strike/commit/9cf2078c3fc39681404e59512b2a86503b49f887
Notes on translatable texts in diffrent files formats
Generate the .po file from the source code, with PoEdit
When all the source code will have been scanned, we'll use this software PoEdit, to scan the source code and locate all added tags : _(...). The software will create the vegastrike-fr_FR.po file, which will contain all translatable texts... magic :)
Translate the .po with PoEdit
Translators will use the same software to open the /data/i18n/LC_MESSAGES/vegastrike-fr_FR.po file, and will have to translate each line... This is less magic ;-)
Progress
Please add here the tree which has been processed. If an entire folder is processed, please don't show all files list, a (*) near the folder name will be enough ;-)
data |---bases (*) (green) | |---fixers (*) (Obu) | |---communications (en cours) (Obu) |---mission (*) I had to re-factor all the .mission for poedit to detect translatable text (costalfy) |---modules (*) (green) | |-------- quests (*) ( ezee )
