See Cuba #2524
Since Cuba 7.2 locales could include script part, e.g. sr-Latn. But locales with script should be defined using IETF BCP 47 language tag and language suffix of associated message pack should also be that language tag.
Locales with country and variant also supported, e.g. en_US (language + country, was supported previously) and ja_JP_JP (language + country + variant, was not supported previously, but it was supposed to be).
I suppose it should also be explained for cuba.availableLocales app property ({language_code} part).
Messages are retrieved from the packs according to the following priority:
1) Check message packs with full name (e.g. messages_sr-Latn.properties for sr-Latn, messages_ja_JP_JP.properties for ja_JP_JP)
2) If not found previously, check language message packs (e.g. messages_sr.properties for sr-Latn, messages_ja.properties for ja_JP_JP) - rules explained in "Message Packs" section starts from that step.
Environment
Description of the enhancement
See Cuba #2524 Since Cuba 7.2 locales could include
scriptpart, e.g.sr-Latn. But locales withscriptshould be defined using IETF BCP 47 language tag and language suffix of associated message pack should also be that language tag. Locales withcountryandvariantalso supported, e.g.en_US(language+country, was supported previously) andja_JP_JP(language+country+variant, was not supported previously, but it was supposed to be). I suppose it should also be explained forcuba.availableLocalesapp property ({language_code}part).Messages are retrieved from the packs according to the following priority: 1) Check message packs with full name (e.g.
messages_sr-Latn.propertiesforsr-Latn,messages_ja_JP_JP.propertiesforja_JP_JP) 2) If not found previously, check language message packs (e.g.messages_sr.propertiesforsr-Latn,messages_ja.propertiesforja_JP_JP) - rules explained in "Message Packs" section starts from that step.