Check for Existing Support
Transifex identifies more than 290+ languages and many more associated with a locale code. These languages adhere to the ISO 639-1 standard of language names and locales. You might fall back to 639-2 or 639-3 if your language is not covered in 639-1. For a full list of supported languages, please refer to our Languages page.
If your language isn't on the Languages page and your files appear in a shortened version like ‘xx_YY', then you can help us provide the necessary information in order to add your language to Transifex.
Check the Unicode standard for Language Plural Rules and check that the rules for your language are correct. If so, let us know. Otherwise, try to find an authoritative source for the correct data and point us to that.
For every language Transifex supports, there's a set of information or rules that are followed by the system. Let's take for example, Brazilian Portuguese:
name: Portuguese (Brazillian)
code_aliases: pt-br pt-BR
pluralequation: (n > 1)
rule_one: n is one
nameis the language name in the 'Language (Nationality)' format. You can omit the nationality for general languages like 'pt'.
codeis ISO 639-1 language code. You might fall back to 639-2 or 639-3 if your language is not covered in 639-1.
code_aliasesare aliases separated with spaces (e.g. pt-br pt-BR).
npluralsis the number of plurals allowed by the language. These are quite common in .po files.
pluralequationis an equation to distinguish the plural rules for the available
nplurals. These are also quite common in .po files, too.
The rule fields MUST reflect the exact number of
nplural set to the language. This means that if your language has nplural = 2, then only 2 of the rule fields must be filled in.
rule_other is considered the general rule. All languages must this rule — even those that do not have plurals (such as Japanese). The
rule_other is considered a general fallback, like an ‘else' statement for all other possible rules. If there is a case that doesn't fit into the
rule_other will be used.