This page provides unofficial guidance for Buriedbornes translators.
We use Zanata to manage translations. Please check the information for translators to get started on Zanata, here. You do not need to be registered as a translator on Zanata to help! You can help with translations in Discord, and find
some sucker a kind person with Zanata permissions to update on your behalf.
Unless you are the only translator for a language, you don't need to use Zanata. If you want a Zanata account: please read the information in the link above, which has instructions on contacting the developer to request permissions to the Buriedbornes translation project. You will be unable to edit until you are approved as a member.
- Join us on Discord. That's where all the translation action occurs.
- If you can't read Japanese, you will have difficulty. You may want to use the English translations as your reference point.
- Work with any foolish/benevolent souls who understand Japanese to help you deconstruct the JA strings. It'll help to translate them as accurately as possible.
- Varience in languages will inevitably mean there may be structural/grammatical differences, but the key concepts, style and context should remain faithful to the Japanese translations.
- Expect to collaborate with others, possibly with those of different languages. We're an international bunch!
- It's better to ask if unsure, rather than possibly mistranslating. Missing translations are easier to spot and fix than incorrect translations, which then rely on a bug report.
- Google Translate is hit-and-miss; use it with caution.
- matchbornes: search for partial strings in Buriedbornes to isolate and troubleshoot translations. Think of it as multilingual grep for buriedbornes.
Key concepts to aid in understanding the context of words, and the style of language to use:
- Consistency is important. Refer to the labels/words used in other strings as indicators, though there may be inconsistencies try to agree with the language team an appropriate word and consistently use it.
- Descriptions: these were written by the author of the Monster Dictionary. Descriptions should read as if from the Dictionary.
- Brevity in descriptions is preferred.
- Enemy skills: avoid explanations/descriptions in the names. It should be "Wrath of Kahn" not "Half Your Health".
EN Current Priorities
Remember that as a community-driven, volunteer effort, nobody is being paid for translations. We do it because we love the game, and we do it only if and when time allows.
- There are hordes of IDs missing translations, usually in formation (blocks of ID numbers). Searching for the string "preparing for translation" will return most of these. We're currently working through them in order, which is a major effort over a long period of time.
- Making it consistent: due to past community-driven efforts (good!) resulting in often fragmented language (bad!), there are many inconsistencies throughout the strings. It is a slow and major effort to reconcile these.
- Fixing buggy translations: we generally rely on reports to fix incorrect translations.
- Except for stats (STR DEX INT PIE), avoid acronyms in descriptions: Cooldown(s), not CD.