| | 1 | [[TOC]] |
| | 2 | |
| | 3 | [[Image(http://main.elivecd.org/images/misc/tux-mexican.png)]] |
| | 4 | |
| | 5 | |
| | 6 | = How to made Translations in Elive = |
| | 7 | |
| | 8 | Please Read entirely this document if you are an Elive translator, it will contain some '''important''' things to know in order to not have problems with your translations (or accidents) |
| | 9 | |
| | 10 | == Requeriments == |
| | 11 | |
| | 12 | Since we have the magnifical tool called '''eltrans''', you don't need anything more to have :) |
| | 13 | |
| | 14 | To have eltrans, you need to have an updated system of Elive (if you are a user of Gem, please read in the bottom) like the development versions, in any case it is very recommended to update the version of eltrans sometimes, so open a terminal and run: |
| | 15 | {{{ |
| | 16 | eliveuser@Elive[~]$ su |
| | 17 | Password: ******* |
| | 18 | root@Elive[/home/eliveuser]# apt-get update && apt-get install eltrans |
| | 19 | }}} |
| | 20 | |
| | 21 | == What I can translate ? == |
| | 22 | |
| | 23 | Just run '''eltrans''' and you can see all the translations that you can made, you can also made translations for Enlightenment 17 but you can't send them in the automatized way of eltrans, for that you need to send your generated translation via email (more instructions in eltrans) |
| | 24 | |
| | 25 | If you want also to made translations for the rest of applications that are not listed (normally, Debian applications), you need to enter in contact with the Debian people and ask them how to made translations for Debian. If the element that you want to translate is not a part of Debian but a part of Elive and it is NOT available on eltrans, you need to request to support this element in eltrans too, for that, just create a new ticket requesting it (or better talk about this on the #elive-dev IRC channel) |
| | 26 | |
| | 27 | == Important things to Know == |
| | 28 | |
| | 29 | This is the important section :) |
| | 30 | |
| | 31 | * '''Fast commits''': Its important to send fast commits in order to not send a translation at the same time that other person (this will do a conflict of versions and then or you fix it manually (following the HowtoSVN tutorial), or you just remove your translation (you lost it)), in order to made fast commits just: |
| | 32 | * Do not think ''I will continue tomorrow'', just send it, tomorrow you will open again eltrans and you will have it again updated. Same if you need to go somewhere for a while |
| | 33 | * If you are doing big translations (only elive translations, not matters for the Enlightenment17 translations), save the document and send it every time that you want (15 minutes?), think on this just like if you are running your previous operating system that sometimes can do a crash and you will lost your document if you have not saved it since a while :] |
| | 34 | * '''Code''': You are translating messages of a source code application, this mean that it will contain strange characters or things like: |
| | 35 | {{{ |
| | 36 | This is a C %s string |
| | 37 | This is a BASH $var variable |
| | 38 | This is another BASH ${var%%/*} type of variable |
| | 39 | This is a \n newline symbol |
| | 40 | }}} |
| | 41 | All these messages (and a lot others) are '''NOT''' errors, they are code, so '''do not''' change them, keep them just as how they are, if not, the application will not work correctly showing the correct messages, this is a correct equivalent example of translating the first line to spanish: ''Esto es una C %s frase'' |
| | 42 | * '''Updates''': Also called ''clowd'' and ''fuzzy'', this means that the message was autogenerated (automatic translations system) or that the origina message was slighty modified, in order words, it needs a simple revision/lookup, just a check if the translation is correct, if don't needs any modification, just click in the '''cloud''' icon in order to mark it as ''OK'' |
| | 43 | |
| | 44 | == Control == |
| | 45 | |
| | 46 | If you want to control the other translations, you will learn [HowtoSVN how to use SVN] to have your own/manual control, or also you can simply use the [http://dev.elivecd.org/timeline timeline] where you can watch the new commits by other users visually, you have a lot of options and ways to do it, you can also have a RSS system in the timeline so that you can watch every commit, to which language, and from who, like: |
| | 47 | {{{ |
| | 48 | Eltrans: auto-sent for |liveboot| in -|es|- by 'Thanatermesis' |
| | 49 | }}} |
| | 50 | ,,'''Note''': Any better suggeriment for this sentence ? This sentence is on this form since the version '''4.1-8''' of eltrans, so everybody that uses this version will send with this format ,, |
| | 51 | |
| | 52 | == Final Notes == |
| | 53 | |
| | 54 | This website is full of features, you can browse translations, also in '''oldest versions''' |
| | 55 | * Imagine that somebody has send a wrong translation and has then broken yours one, just browse the versions going back in the history looking oldest versions, get the desired one, and merge it (its recommended to use the tool ''meld'') in the actual updated version (you should read how to use SVN: HowtoSVN) and send it again |
| | 56 | |
| | 57 | Like the previous example, not only you can browse old versions of code but also compare them with a visual (colored) differencies tool, download as RAW files, as DIFF format, etc etc |
| | 58 | |
| | 59 | In any case you can try anything on the original [http://www.hosted-projects.com/trac/TracDemo/Demo Trac DEMO Website] |
