Editing Locale (computer software) (section)

== Specifics for Microsoft platforms ==

{{outdated|section|date=June 2016}}

Windows uses specific [https://web.archive.org/web/20170228045725/https://msdn.microsoft.com/en-us/library/39cwe7zf(vs.71).aspx language] and [https://web.archive.org/web/20160610104759/https://msdn.microsoft.com/en-us/library/cdax410z(VS.71).aspx territory] strings.
The ''locale identifier'' (LCID) for [[managed code|unmanaged code]] on [[Microsoft Windows]] is a number such as 1033 for English (United States), or 2057 for English (United Kingdom), or 1041 for Japanese (Japan). These numbers consist of a language code (lower 10 bits) and a culture code (upper bits), and are therefore often written in [[hexadecimal]] notation, such as 0x0409, 0x0809 or 0x0411.
[[Microsoft]] is starting to introduce managed code [[application programming interface]]s (APIs) for .NET that use this format. One of the first to be generally released is a function to mitigate issues with [[internationalized domain name]]s,<ref>{{cite web |url=https://msdn.microsoft.com/library/windows/desktop/dd317795.aspx |title=DownlevelGetLocaleScripts function (Windows) |work=[[Microsoft Developer Network|MSDN]] |publisher=[[Microsoft]] |accessdate=2017-12-11}}</ref> but more are in [[Windows Vista]] Beta 1.

Starting with Windows Vista, new functions<ref name="microsoft">{{cite web |url=https://docs.microsoft.com/en-us/windows/win32/intl/locale-names |title=Locale Names (Windows) |work=[[Microsoft Developer Network|MSDN]] |publisher=[[Microsoft]] |accessdate=2017-12-11}}</ref> that use [[BCP 47]] locale names have been introduced to replace nearly all LCID-based APIs.

A POSIX-like locale name format of {{mono|language[_country-region[.code-page]]}} is available in the UCRT (Universal C Run Time) of Windows 10 and 11.<ref>{{cite web |title=Locale Names, Languages, and Country-Region Strings |url=https://learn.microsoft.com/en-us/cpp/c-runtime-library/locale-names-languages-and-country-region-strings?view=msvc-140 |website=learn.microsoft.com |language=en-us |date=19 October 2022}}</ref>