Managing custom project locales
Loco has hundreds of the most common locales pre-defined, but there's a lot more control available if you need it.
- When adding a new locale, switch to "Custom" mode to define the exact locale you need;
- When editing an existing locale you can change any of its properties at any time.
The only mandatory field is the language. When editing a custom locale just start typing a language into this field and it will auto-complete. This list contains over 7,000 standard codes.
The most common language-region combinations are available from the pre-defined list, but here you can create any combination you need. The list of available regions includes 249 countries and 30 UN regions. Just start typing and the region will auto-complete.
Region is optional, so if you have a locale like
"en-GB" you can blank this field out to get just
Loco automatically creates a 'Friendly name' from language and region combinations (such as "English (UK)") but you can customize this, for example by entering "British English".
Note that changing other properties of a locale might cause this name to be regenerated.
These additional properties are available by default. If you don't see these options, check your project's legacy settings.
The "script" field can be used to define an alternative written style for a given language. A common example is differentiating between Traditional and Simplified Chinese. This list contains 173 standard codes.
The "variant" field is for defining specific dialects or other language variations. This list contains the 72 variant codes recognized by IANA.
The "extension" field can be used to add a non-standard suffix to your locale code. This is a free-text value following a specific format.
Loco automatically creates plural rules for your chosen language according to Unicode's CLDR. If you need to override this, you can define custom plural rules in the locale edit window. Read more about Plural forms in Loco.
If you have developer permissions, you can modify how a locale is represented across various platforms via the Developer tab. These options are primarily for interacting with the API.
See developer support for information on these advanced locale settings.