Locus GIS is available in many World languages. This is thanks to the crowd-sourcing project Crowdin.com and volunteering Locus GIS 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 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
At the end of every year, we reward the best performing translators with LoCoins and other prizes.
Best UX practices
Before you get to work, please read these basic premises of UX texts in Locus GIS :
Clear - Jargon-free, offering context
- don’t use technical terms (e.g. failure, invalid, database, authentication… etc.)
- pay attention to verbs as the most powerful words carrying action
- focus on the user
Concise - Economical and frontloaded
- write shortly and efficiently
- make sure every word on the screen has a distinct job
- put your important message first
Positive - Respecting Locus GIS ’s brand voice
Locus GIS 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.
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.
Example:
Action can not be done now.\n\nTry again later! Akci nelze vykonat\n\nZkuste to znovu později! Application \'%s\' not installed Aplikace \'%s\' není nainstalována