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 fallback 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 in the Languages page and your files appear in a shortened version like ‘xx_YY', then you can help us providing the necessary information in order to add your language into Transifex.

SHORT VERSION

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.

LONG VERSION

For every language Transifex supports, there's a set of information or rules that's followed by the system. Let's take for example Brazilian Portuguese:

  • name: Portuguese (Brazillian)

  • code: pt_BR

  • code_aliases: pt-br pt-BR

  • nplurals: 2

  • pluralequation: (n > 1)

  • rule_zero: -

  • rule_one: n is one

  • rule_two: -

  • rule_few: -

  • rule_many: -

  • rule_other: -

In detail:

  • name is the language name in the 'Language (Nationality)' format. You can omit the nationality for general languages like 'pt'.

  • code is ISO 639-1 language code. You might fallback to 639-2 or 639-3 if your language is not covered in 639-1.

  • code_aliases are aliases separated with spaces (e.g pt-br pt-BR).

  • nplurals is the number of plurals allowed by the language. These are quite common in .po files.

  • pluralequation is 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.

The 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 pluralequation, rule_other will be used.

Examples can be found here. We usually get rule information from unicode.org.

When we add support for a language we follow the BCP47 standard. The multiple language locales are based on region subtags.


Continue Reading

General Questions

Managing Projects

Translating Content

Collaborating

Accounts and Billing

Back to Help Center

Did this answer your question?