M3 MT Cloud: Where is the definition for the Locale and from where does the configurable xml picks t

Legacy Contributor

Hi,

We are having a issue in OIS199PF with the date format

We need to know from where does the configurable xml picks the locale.

Customer in Thailand the locale is TH.
Customer in Philippines the locale is en-PH.

This is seen in configurable xml itself.

I revisited the m3 programs CRS010 and CRS045 but could not find any difference.

As in CRS010 there is no entry for either TH or PH but in CRS045 there is entry of both.

We need to know from where this en-PH is coming in configurable xml why not only PH like in case of thailand customer TH.

We feel this is a M3 setting itself as the config xml is coming from M3.


Best Regards
Shashank Malali

martin-jarrolf

Some details for how the locale is intended to work in M3:

Locale 

A set of parameters that defines the user's language, region and any special variant preferences that the user wants to see in their user interface. Usually a locale identifier consists of at least a language identifier and a region identifier. (Wikipedia)

Locale uses the format xx-YY

xx = ISO code for language (CRS010 - Language. Open)

YY= ISO code for country (CRS045 - Country. Open)

Language		Country		Locale
M3 code	ISO code	M3 code	ISO code
GB	en	US	US	en-US
GB	en	GB	GB	en-GB
DE	de	DE	DE	de-DE
SE	sv	SE	SE	sv-SE

Preferred Locale

There are cases wherein the setup in CRS010 and CRS045 does not perfectly matches a locale. In this case, some guesswork is necessary to pick the nearest correct locale.

The combination of the document language ISO code and the from-to country ISO code determines the language tag used in the look up mechanics to find the preferred locale (logic is based on RFC 4647 - Matching of language tags).

The preferred locale is matched against the list provided here: External link

A hierarchy is introduced to find the best matching language tag in difference scenarios.

The hierarchy is as follows:

1. Find language tag using both language and country ISO code with the goal of finding an exact match. (e.g. "en-GB")
2. If not found, find language tag using only the language ISO code with the goal of prioritizing the locale language. (e.g. "en-*)
3. If not found, find the language tag using only the country ISO code with the goal of finding the best matching language for a country code(e.g. "*-GB")
4. If not found and the language ISO code is given, use it (e.g. "se" for Northern Sami). This is to cover the fact that the list from JAVA is not definitive and could be missing some locales. There is a validation in CRS010 that verifies input language against ISO-639-1.
5. If all options are exhausted, default to using "en-GB" as locale.

Use-case examples: Languages: en = English, ja = Japanese, sv = Swedish, *se = Northern Sami, Countries: GB = Great Britain, US - United States, JP - Japan, *WW = not an existing country Note: * - not in the locale list, -Test with both language and country:

• Language ISO "en" Country ISO "US" would produce locale "en-US"
• Language ISO "en" Country ISO "JP" would produce locale "en"
• Language ISO "se" Country ISO "JP" would produce locale "ja-JP"
• Language ISO "se" Country ISO "WW" would produce locale "se"

Use cases with country only: 5. Language ISO "" Country ISO "JP" would produce locale "ja-JP"

•  Language ISO "" Country ISO "WW" would produce locale "en-GB"

Use cases with language only. Although its hypothetical since CRS045 does not allow blank country code ISO:

•  Language ISO "sv" Country ISO "" would produce locale "sv-SE"
•  Language ISO "se" Country ISO "" would produce locale "se"

Use case with both language and country are left blank. Although its hypothetical since CRS045 does not allow blank country code ISO:

• Language ISO "" Country ISO "" would produce locale "en-GB"