sections in the article
A Language, sometimes referred to as a locale, is one of the building blocks of inriver's Elastic Data Model.
For detailed information about language options in inriver, read this article.
For instructions on how to change languages, read this article.
Selecting model languages
When building a data model, you decide in what language(s) your content needs to be presented.
The available languages are listed in ISO 639, a standard covering most of the languages in the world.
Every language has a code that consists of two parts, the second being optional. The first part of the code is the code (2 or 3 characters) for the actual language, the second optional part, following after a dash, is if you want to specify a country code (2 characters) version of the language used in a specific country.
Spanish, for example, is a language used as native language in a lot of countries, but the versions spoken in Spain, Mexico and the Philippines may vary a lot, and your content may have to be different when you market your products in those countries. Therefore, you can include several country specific versions of a language in a data model.
Read about the ISO 639 code of more than 800 languages that are supported in inriver in this article.
Below is a list of language code examples:
|English (United Kingdom)
|English (United States)
|Spanish (Spain, international Sort)
Adding a model language
Languages (locales) are managed in inriver using the object LocaleString.
You work with languages in Control Center > Model. Read more in this article.
When adding a language to a data model in Control Center > Model > Language, you enter the ISO 639 code.
When you have added a language to your model, it turns up as a language layer in user interfaces for field types that are of type LocaleString. Language layers also turns up in CVL:s of type LocaleString and in Control Center > Model where you can translate the names of your model objects.
You don’t need to add all model languages from the start. You can add them one by one when you need to. This is quite common when you expand to new markets.
Technically, languages are handled as .NET CultureInfo objects. .NET provides CultureInfo information for all ISO 639 languages. Read more about globalization with CultureInfo in this article.