Rules and guidelines for managing multilingual assets
Consider the following rules and guidelines when you manage multilingual assets:
•Before you set an attribute as multilingual, remove all rule associations configured for the attribute. You can't set an attribute with a rule association as multilingual.
•After you enable the multilingual property and save the asset, you can't disable the property or add rule associations to the attribute.
•You can set only string attributes as multilingual, such as Name and Description. You can't set the Code attributes as multilingual.
•You can't set default values for multilingual attributes. When you set an attribute as multilingual, Reference 360 clears the default value that you previously set for the attribute.
•You can't remove an additional language for a code list if a code value contains data in that language. To remove the language, clear the values for that language from all code values in the code list.
•You can't sort code values based on multilingual attributes on the Values tab of a multilingual code list.
•When you export a code list at a point in time that precedes localization, the export file contains only the Code attributes, and you can't export localized attributes, such as Name and Description.
•Don't use the reserved words _language and _localizedContent as attribute names. For a complete list of reserved keywords, see Reserved keywords.
•When you view an attribute value in a language for which no value is stored, Reference 360 displays an empty value for that language. For example, you set the Status attribute as multilingual and store values in English (en-US) and French (fr-FR). When you choose to view the value in Japanese (ja-JP), Reference 360 returns an empty value because no Japanese value is stored for the attribute.
•When you configure a combination of display attributes, such as a concatenation of the Name, Code, and Description, to represent code values in other assets, and if a multilingual attribute has no stored value, Reference 360 shows an empty string for each field that has no value in the preferred language. For example, you might want the Code, Name, and Description attributes to represent code values in the Country Codes code list. You might have a code value with the Name as Canada, the Code as 124, and no stored value for the Description attribute in the preferred language. When the code value appears in other assets, it appears as 124 Canada. For more information about configuring display attributes, see Configuring display attributes.
•In the exported CSV file, the number of rows is based on the number of target languages, and the file includes the _language and _localizedContent fields. During import, the import process automatically maps the _language and _localizedContent fields.
•During file import, you can import data for a language code that isn't in the Localization Languages code list. The import doesn't require a value for the default language. The import lets you skip the value for the default language though a value for the default language is mandatory. For example, you import a code value with the language code fr-FR, which isn't in the Localization Languages code list but is a valid BCP 47 code. If en-US is the default language, Reference 360 requires a value for the Name (en-US) attribute. However, the import doesn't require it, and the import completes successfully because the language code is valid.