Skip to content

[Feature Request]: add language support for mk_MK, cnr_ME, sr_Cyrl_RS #8163

@ilhan007

Description

@ilhan007

Feature Request Description

The request is to support mk_MK, cnr_ME, sr_Cyrl_RS languages in UI5 Web Components.

However, before any implementation on our side, there are 3 dependant tasks that needs to be completed:

  • LX Lab Team to provide the translation of the the message bundle entries for the respective languages
  • SAPUI5 Core colleagues to update the CLDR resources and clarify the fallback mechanism (which CLDR/ messagebundle should be fetched for all combinations - sr, sr-RS, sr-Cyrl-RS, etc. see below)

Afterwards, we need to:

  • update the CLDRs
  • make sure we properly fetch, fallback the respective CLDRs and message bundles for the respective languages

Proposed Solution

Take the latest CLDR when available on NPM and implement the following fetch and fallback mechanism:
*language -> CLDR, messagebundle

  • ?sap-ui-language=sr
    -> sr.json, messagebundle_sr.properties

  • ?sap-ui-language=sr-RS
    -> sr.json, first messagebundle_sr_RS.properties, if not found then messagebundle_sr.properties

  • ?sap-ui-language=sh
    -> sh.json, messagebundle_sh.properties

  • ?sap-ui-language=sh-RS
    -> sr.json, first messagebundle_sh_RS.properties, if not found then messagebundle_sh.properties

  • ?sap-ui-language=sr-Cyrl-RS
    -> sr.json, first messagebundle_sr_RS.properties, if not found then messagebundle_sr.properties

  • ?sap-ui-language=sr-Latn
    -> sh.json, messagebundle_sh.properties

  • ?sap-ui-language=sr-Latn-RS
    -> sh.json, first messagebundle_sh_RS.properties, if not found then messagebundle_sh.properties

  • ?sap-ui-language= mk_MK
    -> mk.json, first messagebundle_mk_MK.properties, if not found then messagebundle_mk.properties

  • ?sap-ui-language=mk
    -> mk.json, messagebundle_mk.properties

  • ?sap-ui-language= cnr_ME
    -> cnr.json, first messagebundle_cnr_ME.properties, if not found then messagebundle_cnr.properties

  • ?sap-ui-language=cnr
    -> cnr.json, messagebundle_cnr.properties

Proposed Alternatives

No response

Organization

SuccessFactors

Additional Context

No response

Priority

High

Privacy Policy

  • I’m not disclosing any internal or sensitive information.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Completed

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions