User Tools

Site Tools


manual:about:translation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
manual:about:translation [2017/09/29 11:47] mstupkamanual:about:translation [2021/09/07 10:29] (current) mstupka
Line 1: Line 1:
 ====== Locus Map translation ====== ====== Locus Map translation ======
  
-Locus Map is available in many World languages. This is thanks to crowdsourcing project **[[https://crowdin.com/project/menion|Crowdin.com]]** and helpful Locus Map users from many countries who participate in it. +Locus Map is available in many World languages. This is thanks to the crowd-sourcing project **[[https://crowdin.com/project/menion|Crowdin.com]]** and **volunteering Locus Map users** from many countries who helpfully participate in it.  
 + 
 +===== Are you willing to help us with translations too? ===== 
 +  * **sign up** for our Locus project at **[[https://crowdin.com/project/menion|Crowdin.com]]** 
 +  * **write a few words** about your intentions **in English** in the Crowdin application form so that we know **you can speak English** 
 +  * wait for the **approval** 
 +  * **WELCOME ABOARD!** 
 + 
 +<WRAP center round tip> 
 +At the end of every year, **we reward the best performing translators** with LoCoins and other prizes. 
 +</WRAP>
  
-**Are you willing to help us with translations? WELCOME ABOARD!** 
  
 ---- ----
Line 10: Line 19:
 Before you get to work, please read these basic premises of UX texts in Locus Map: Before you get to work, please read these basic premises of UX texts in Locus Map:
 ==== Clear ==== ==== Clear ====
-**Jargon free, offering context**+**Jargon-free, offering context**
   * don’t use technical terms (e.g. failure, invalid, database, authentication… etc.)   * don’t use technical terms (e.g. failure, invalid, database, authentication… etc.)
   * pay attention to verbs as the most powerful words carrying action    * pay attention to verbs as the most powerful words carrying action 
Line 27: Line 36:
 Locus Map is an application for people who use it mainly in their leisure time spent outdoors with **friends or family**. Locus Map wants to be **one of your friends**. It wants to be **reliable, helpful, dedicated, reassuring**. Therefore, it wants to express **casually, whimsically, even warmly** - just like **good friends do**. Locus Map is an application for people who use it mainly in their leisure time spent outdoors with **friends or family**. Locus Map wants to be **one of your friends**. It wants to be **reliable, helpful, dedicated, reassuring**. Therefore, it wants to express **casually, whimsically, even warmly** - just like **good friends do**.
  
-On the other hand, in case of an issue when **user can’t get what he wants** (out of GPS signal, missing routing data pack etc.), Locus does NOT mock the user - it always **tries to help**, not making fun of it - **never use negatives** like "never", "bad" etc+On the other hand, in case of an issue when **user can’t get what he wants** (out of GPS signal, missing routing data packetc.), Locus does NOT mock the user - it always **tries to help**, not making fun of it - **never use negatives** like "never", "bad" etc.
-===== Technical issues ===== +
- +
-==== Plurals ==== +
- +
-Crowdin.com is not able to handle **Android plural system** correctly. So you're directly translating XML source file instead of the text. +
- +
-It is also not possible to define which "quantity" identifiers you need, so as you can see, we had to define all six possibilities, even if they're often the same. But they're not of course the same in all languages. +
- +
-What "quantity" means is in the table below. Complete description is [[http://developer.android.com/guide/topics/resources/string-resource.html#Plurals|here >>]] if you're interested.+
  
-<html> 
-          <table> 
-            <tr><th>Value</th><th width="500px">Description</th></tr> 
-            <tr> 
-              <td><code>zero</code></td><td>When the language requires special treatment of the number 0 (as in Arabic).</td> 
-            </tr> 
-            <tr> 
-              <td><code>one</code></td><td>When the language requires special treatment of numbers like one (as with the number 1 in English and most other languages; in Russian, any number ending in 1 but not ending in 11 is in this class).</td> 
-            </tr> 
-            <tr> 
-              <td><code>two</code></td><td>When the language requires special treatment of numbers like two (as in Welsh).</td> 
-            </tr> 
-            <tr> 
-              <td><code>few</code></td><td>When the language requires special treatment of "small" numbers (as with 2, 3, and 4 in Czech; or numbers ending 2, 3, or 4 but not 12, 13, or 14 in Polish).</td> 
-            </tr> 
-            <tr> 
-              <td><code>many</code></td><td>When the language requires special treatment of "large" numbers (as with numbers ending 11-99 in Maltese).</td> 
-            </tr> 
-            <tr> 
-              <td><code>other</code></td><td>When the language does not require special treatment of the given quantity.</td> 
-            </tr> 
-          </table> 
-</html> 
 ==== Untranslatable code elements ==== ==== Untranslatable code elements ====
  
-There are a few elements that are not subject of translation but are compulsory for all language versions - they must remain a part of the translated phrase. They are various formatting tags, variables etc.+There are a few elements that are not subject to translation but are compulsory for all language versions - they must remain a part of the translated phrase. They are various formatting tags, variablesetc.
  
 <WRAP center round box > <WRAP center round box >
manual/about/translation.1506678458.txt.gz · Last modified: 2017/09/29 12:47 (external edit)