Changes between Version 4 and Version 5 of HowtoTranslators


Ignore:
Timestamp:
02/04/16 14:21:30 (20 months ago)
Author:
thanatermesis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowtoTranslators

    v4 v5  
    44 
    55 
    6 = How to made Translations in Elive = 
     6= How to make Translations in Elive = 
    77 
    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) 
     8This document contains some '''important''' things to know in order to not have problems with your translations 
    99 
    1010== Requirements == 
    1111 
    12 Since we have the magnificent tool called '''eltrans''', you don't need to have anything more :) 
     12We have an own made tool that makes the translations very easy, try to run it from the Applications menu or pressing "Alt + Esc" in your desktop, its called '''eltrans'''. 
    1313 
    14 To have eltrans, you need to have an updated system of Elive (if you are a user of Gem, please read 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: 
     14If you don't have it installed, you can install it like this: 
     15 
    1516{{{ 
    1617eliveuser@Elive[~]$ su 
    1718Password: ******* 
    18 root@Elive[/home/eliveuser]# apt-get update && apt-get install eltrans 
     19root@Elive[/home/eliveuser]# apt-get update ; apt-get install eltrans 
    1920}}} 
     21 
    2022 
    2123== What can I translate ? == 
    2224 
    23 Just run '''eltrans''' and you can see all the translations that you can make. You can also make translations for Enlightenment 17 but you can't send them in the automatized way, for that you need to send your generated translation via email (more instructions in eltrans) 
     25When you run the '''eltrans''' tool you can see all the applications of Elive that you can translate. You can also make translations for Enlightenment 17 but you can't send them in the automatized way, for that you need to send your generated translation via email (more instructions in eltrans) 
    2426 
    25 If you want to translate for applications that are not listed (normally, Debian applications), you need to contact the Debian people and ask them how to make 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) 
     27Finally, if you want to translate for applications that are not listed (normally, Debian applications), you need to check how Debian does it, which is a different process. 
     28 
     29If 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) 
    2630 
    2731== Important things to Know == 
     
    2933This is the important section :) 
    3034 
    31  * '''Fast commits''': Its important to send fast commits in order to not send a translation at the same time as another person (this will do a conflict of versions or you fix it manually (following the HowtoSVN tutorial), or you just remove your translation (you lost it)), in order to make 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 (15 minutes?), think on this just like if you are running your previous operating system that sometimes it can crash and you will lose your document if you have not saved it in a while :] 
    34  * '''Code''': You are translating messages of a source code application, this means that it will contain strange characters or things like: 
     35 * '''Fast commits''': Its a good practice to send your translations not much delayed, like every hour, this is important so that if somebody else is working on the same translation too it will not conflict between versions of the file. If this happens you can try to fix it manually (following the HowtoSVN tutorial) if you have some developer knowledges (svn in fact) but eltrans can make it a little easier for you too, if you want to continue your translations in another moment just send the actual made ones before to close ''eltrans'': 
     36 * '''Code''': You are translating messages of a source code application, this means that it will contain strange things like: 
    3537{{{ 
    3638This is a C %s string 
    3739This is a BASH $var variable 
    3840This is another BASH ${var%%/*} type of variable 
    39 This is a \n newline symbol 
     41This is a \n newline symbol (escape secuence to reprent an 'Enter') 
    4042}}} 
    41    All these messages (and a lot others) are '''NOT''' errors, they are code, so '''do not''' change them, keep them just as 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 ''cloud'' and ''fuzzy'', this means that the message was auto-generated (automatic translations system) or that the original message was slightly modified, in other words it needs a simple revision/look-up, just a check if the translation is correct, if it doesn't need any modifications click in the '''cloud''' icon in order to mark it as ''OK'' 
     43   All these messages (and a lot others) are '''NOT''' errors, they are code, so '''do not''' change them, keep them just as they are, if not, the application will not work correctly showing the correct messages, specially the ones like '''%s'''. This is an example of a translation to Spanish for the first line: ''Esto es una C %s frase'' 
     44 * '''Updated sentences''': Also called ''fuzzy'' or represented as a ''cloud'', this means that the message was auto-generated (automatic translations system) or that the original message was slightly modified, in other words it needs a simple revision/look-up, just a check if the translation is correct and equivalent to the original message, if it doesn't need any modifications click in the '''cloud''' icon in order to mark it as ''OK''. 
    4345 
    4446== Control == 
    4547 
    46 If you want to control the other translations, you will learn [HowtoSVN how to use SVN] to have your own/manual control, or 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: 
     48If you want to have more control to the translations, check [HowtoSVN how to use SVN] to understand how it works internally. You can also check the [http://dev.elivecd.org/timeline timeline] where you can watch the new commits by the other translators in a nice and visually way, you can also have a RSS system in the timeline so that you can watch every commit in your News reader, to which language, and from who, like: 
    4749{{{ 
    4850Eltrans: auto-sent for |liveboot| in -|es|- by 'Thanatermesis' 
    4951}}} 
    50 ,,'''Note''': Any better suggestion 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 ,,[[BR]] 
    51 ,,'''Note''': Maybe you will see commits like in [983] sent by ''Automatic Translations Generator'' that looks strange... do not worry about them, in a fast look you can see that there's nothing changed, it is just the automatic-translations-generator script that changes the columns number (needed for its correct work), so it compress all the message in a single line, but there's no modification on it 
    5252 
    53 == Final Notes == 
     53You can also check for older versions of the translations since they are saved in the history, that's called ''svn revisions'' 
    5454 
    55 This website is full of features, you can browse translations, also in '''oldest versions''' 
    56  * Imagine that someone has sent a wrong translation and has then broken yours, 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 
     55 * Example: Imagine that someone has sent a wrong translation and has then broken yours, so 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 (how to use SVN: HowtoSVN) and send it again 
    5756 
    58 Like the previous example, not only you can browse old versions of code but also compare them with a visual (colored) differences tool, download as RAW files, as DIFF format, etc etc 
    59  
    60 In any case you can try anything on the original [http://www.hosted-projects.com/trac/TracDemo/Demo Trac DEMO Website]