Differences

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

--- manual:about:translation [2015/09/09 11:59] – mstupka
+++ manual:about:translation [2021/09/07 10:29] (current) – mstupka
@@ Line 1: / Line 1: @@
-===== Locus Map translation =====
+====== Locus Map translation ======
-<WRAP todo round center 60%>This page is obsolete and will be reworked soon</WRAP>
+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.
-==== Global ====
+===== Are you willing to help us with translations too? =====
-Locus Map has been translated into many World languages. The translating process is provided by crowdsourcing project **[[https://crowdin.com/project/menion|Crowdin.com]]**. Anybody who is willing to help with translations is welcome.
+  * **sign up** for our Locus project at **[[https://crowdin.com/project/menion|Crowdin.com]]**
-==== Plurals ====
+  * **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!**
-Crowdin is not able to handle Android plural system correctly. So you're directly translating XML source file instead of texts itself.
+<WRAP center round tip>
+At the end of every year, **we reward the best performing translators** with LoCoins and other prizes.
+</WRAP>
-There is also not possible to define by your own, which "quantity" identifiers you need, so as you can see, I had to define all six possibilities, even if they're often same. But they're not of course same in all languages
-What "quantity" mean is in below table. Complete description is [[http://developer.android.com/guide/topics/resources/string-resource.html#Plurals|here]] if you're interested
+----
-<html>
+===== Best UX practices =====
-          <table>
+Before you get to work, please read these basic premises of UX texts in Locus Map:
-            <tr><th>Value</th><th width="500px">Description</th></tr>
+==== Clear ====
-            <tr>
+**Jargon-free, offering context**
-              <td><code>zero</code></td><td>When the language requires special treatment of the number 0 (as in Arabic).</td>
+  * don’t use technical terms (e.g. failure, invalid, database, authentication… etc.)
-            </tr>
+  * pay attention to verbs as the most powerful words carrying action
-            <tr>
+  * focus on the user
-              <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>
+==== Concise ====
-            <tr>
-              <td><code>two</code></td><td>When the language requires special treatment of numbers like two (as in Welsh).</td>
+**Economical and frontloaded**
-            </tr>
+  * write shortly and efficiently
-            <tr>
+  * make sure every word on the screen has a distinct job
-              <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>
+  * put your important message first
-            </tr>
-            <tr>
+==== Positive ====
-              <td><code>many</code></td><td>When the language requires special treatment of "large" numbers (as with numbers ending 11-99 in Maltese).</td>
+**Respecting Locus Map’s brand voice**
-            </tr>
-            <tr>
+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**.
-              <td><code>other</code></td><td>When the language does not require special treatment of the given quantity.</td>
-            </tr>
+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.
-          </table>
-</html>
+==== Untranslatable code elements ====
+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, variables, etc.
+<WRAP center round box >
+**Example:**
+  * Action can not be done now.**\n\n**Try again later!
+  * Akci nelze vykonat**\n\n**Zkuste to znovu později!\\ \\
+  * Application **\'%s\'** not installed
+  * Aplikace **\'%s\'** není nainstalována
+etc.
+</WRAP>
+<WRAP center round important>
+These elements must not be omitted! Their removal could cause instability of the application.
+</WRAP>

knowledge base

User Tools

Site Tools

Differences