The sole purpose of this repository is to allow Nebulous players to collectively improve the translated text used in Nebulous.io [Android][iOS]. Include your Nebulous ID in your PR (Pull Request) comments and you may be granted the translator tag in the game and discord after your PR is approved and merged. Low quality translations (those receiving a high number of comments compared to the number of translations done), will not receive a tag.
If you have general questions or a suggestion, create an issue. You can also submit a suggestion in the discord.
If you have an improvement to make, edit a file and submit a pull request. Pay special attention to the use of placeholders (ex: %) and formatting. Changes to the formatting of the file will not be accepted.
Open the res folder to see all of the supported languages. res/values contains the English strings used as the default for any non-translated strings. Translations should be based on that file.
- Only edit files for which you are a native speaker or have fluency.
- Try not to change the length of a string too much from the length in the English version. The app UI layout is tested with those string lengths.
- Do not submit auto translations (Google Translate, Chat GPT, etc). This is not helpful.
- Adding comments to your PR that explains why subtle changes were made can help. If you are revising something that is already translated, an explanation is required.
res/values: English
res/values-af: Afrikaans
res/values-ar: Arabic
res/values-az: Azerbaijani
res/values-b+es+r419: Spanish (Latin America)
res/values-bg: Bulgarian
res/values-bn: Bengali
res/values-bs: Bosnian
res/values-ca: Catalan
res/values-cs: Czech
res/values-da: Danish
res/values-de: German
res/values-el: Greek
res/values-es: Spanish
res/values-et: Estonian
res/values-fi: Finnish
res/values-fr: French
res/values-ga: Irish
res/values-hi: Hindi
res/values-hr: Croatian
res/values-hu: Hungarian
res/values-in: Indonesian
res/values-is: Icelandic
res/values-it: Italian
res/values-ja: Japanese
res/values-ka: Georgian
res/values-kk: Kazakh
res/values-ko: Korean
res/values-ku: Kurdish (Kurdî)
res/values-lt: Lithuanian
res/values-lv: Latvian
res/values-mk: Macedonian
res/values-mr: Marathi
res/values-ms: Malay
res/values-nl: Dutch
res/values-no: Norwegian
res/values-pl: Polish
res/values-pt-rBR: Portuguese (Brazil)
res/values-pt-rPT: Portuguese (Portugal)
res/values-ro: Romanian
res/values-ru: Russian
res/values-si: Sinhala
res/values-sk: Slovak
res/values-sq: Albanian
res/values-sr: Serbian
res/values-sv: Swedish
res/values-ta: Tamil
res/values-th: Thai
res/values-tl: Tagalog (Pilipino)
res/values-tr: Turkish
res/values-uk: Ukrainian
res/values-vi: Vietnamese
res/values-zh-rCN: Chinese (Simplified)
res/values-zh-rTW: Chinese (Traditional)
When translating content, especially in a consistent and systematic manner, it's important to adhere to the following general tips:
- Consistency in Terminology
- Always use the same terms for specific concepts. If you choose to translate one concept/name some way, use it every time that concept/name appears.
- Maintain consistency in acronyms and capitalizations. For example, use the translation for "XP" or "CTF" consistently without variation.
- Voice Consistency
- Decide early whether the translation will be in a formal or informal voice, and stick to it throughout the entire text.
- Avoid Unnecessary Punctuation
- Do not add a period (.) at the end of strings unless it is required by the original text or grammar rules.
- Keep in mind that some platforms or coding environments may treat punctuation differently, so avoid adding extra punctuation.
- Speaking of which, ellipsis are preferred over 3 periods. An example follows: … (ellipsis) vs. ... (3 periods).
- Consistency in Formatting
- Keep a uniform format with the original. If "Hour" is used, always use the translation with the first letter in caps; same applies otherwise if it's all caps, for example.
- Contextual Accuracy
- Translate based on context to maintain the meaning and tone of the original text. Avoid direct translations that might change the intended message.
- Ensure that terms like "hoarder" or "mogul" are translated in a way that fits the context—either retaining the original term if it’s widely understood or choosing an appropriate equivalent in the target language. AND BE CONSISTENT WITH IT.
- Uniform Length and Structure
- Aim for similar length and structure between the original and translated text, especially if space is limited.
- Break down complex sentences to mirror the original's readability and clarity.
- Cultural Adaptation
- Ensure that cultural references, idioms, or colloquialisms are translated or adapted to be understandable in the target culture. Pay mind to terms like "hat-trick", which tends to have translations depending on the language (remember to always do RESEARCH); or "Doge", which doesn't have a translation.
- Proofreading and Review
- After translation, review the text to ensure consistency in terminology, voice, and formatting.
- Ideally, have another person who is fluent in the language review the translation to catch any inconsistencies or errors you might have missed.
You can always message @critikangel on Discord for help, advice, or support.
Submit an issue. Include a screenshot of the text and any relevant actions you performed.
If a language is missing a line of text, see if it's in values (English). If it is, and it has the translatable=false tag, you can:
- Add it to another language file in the same order as the English file
- Change the tag to
translateable=true - Translate it.
This project is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 4.0 International License. © 2024 Simplicial Software LLC
You are free to:
- Share — copy and redistribute the material in any medium or format
Under the following terms:
- Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
- NonCommercial — You may not use the material for commercial purposes.
- NoDerivatives — If you remix, transform, or build upon the material, you may not distribute the modified material.
For the full license text, please visit http://creativecommons.org/licenses/by-nc-nd/4.0/.