Update language format from ll_CC to LCID

[dreddy-work]

Related to #9556

loc team says ll-CC format is not working for some reason and suggested to change the format to LCID.

Microsoft Reviewers: Open in CodeFlow

[elachlan]

CC: @DJm00n

@dreddy-work aren't LCIDs deprecated?

[dreddy-work]

@dreddy-work aren't LCIDs deprecated?

LCIDs in this PR are used for Loc translation by an internal tool. The way our pipeline setup, it seems loc tools confused between fr and fr-FR and suggested us to use LCID instead, to avoid it.

[elachlan]

This will be a pain to maintain in the future. Is it possible to raise an issue to change it back once the internal tool's issue is resolved?

[Tanya-Solyanik]

Please get an approval from the loc team

[dreddy-work]

This will be a pain to maintain in the future. Is it possible to raise an issue to change it back once the internal tool's issue is resolved?

I don't expect these files to change except for adding new strings. And we do not use Locked attribute on new strings. Regarding the deprecation of LCIDs, where did you read it? LCIDs are used all over .NET (language specific URLs for documentation or product download redirections use them)

[elachlan]

It was mentioned in #8573.

It was under: https://learn.microsoft.com/en-us/globalization/locale/standard-locale-names#the-deprecation-of-lcids

But it looks like that was removed? I can't find it via wayback archive.org

Edit: another link: https://learn.microsoft.com/en-us/globalization/locale/other-locale-names

[DJm00n]

@dreddy-work

it seems loc tools confused between fr and fr-FR and suggested us to use LCID instead, to avoid it.

maybe you can just use LCID for this fr case alone then? anywayszh-Hant language tag is preserved in your change...

[DJm00n]

@dreddy-work

Regarding the deprecation of LCIDs, where did you read it? LCIDs are used all over .NET (language specific URLs for documentation or product download redirections use them)

Here:

LCIDs are being deprecated, and implementers are strongly encouraged to use locale names instead. LCIDs can be used for backward compatibility, but as noted in section 2.2.1, there is no guarantee of LCID uniqueness when used with valid locale names not otherwise associated with an LCID.

and also dotnet/runtime#82367 (comment)