Changes between Version 3 and Version 4 of HowtoTranslators


Ignore:
Timestamp:
Oct 23, 2009, 5:07:56 AM (15 years ago)
Author:
Leo Fortey
Comment:

grammar corrections. minor spelling mistakes.

Legend:

Unmodified
Added
Removed
Modified

  • HowtoTranslators

    v3 v4  
    88Please 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)
    99
    10 == Requeriments ==
     10== Requirements ==
    1111
    12 Since we have the magnifical tool called '''eltrans''', you don't need anything more to have :)
     12Since we have the magnificent tool called '''eltrans''', you don't need to have anything more :)
    1313
    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:
     14To 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:
    1515{{{
    1616eliveuser@Elive[~]$ su
    … …  
    1919}}}
    2020
    21 == What I can translate ? ==
     21== What can I translate ? ==
    2222
    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)
     23Just 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)
    2424
    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)
     25If 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)
    2626
    2727== Important things to Know ==
    … …  
    2929This is the important section :)
    3030
    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:
     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:
    3232   * 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:
     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:
    3535{{{
    3636This is a C %s string
    … …  
    3939This is a \n newline symbol
    4040}}}
    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''
     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''
    4343
    4444== Control ==
    4545
    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:
     46If 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:
    4747{{{
    4848Eltrans: auto-sent for |liveboot| in -|es|- by 'Thanatermesis'
    4949}}}
    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 ,,[[BR]]
     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]]
    5151,,'''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
    … …  
    5454
    5555This website is full of features, you can browse translations, also in '''oldest versions'''
    56  * 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 * 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
    5757
    58 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
     58Like 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
    5959
    6060In any case you can try anything on the original [http://www.hosted-projects.com/trac/TracDemo/Demo Trac DEMO Website]