From 2fed8e5159f7578fccbaced1373eda043407144b Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Fri, 20 Mar 2026 10:14:46 -0500 Subject: [PATCH 1/2] Add note about fallback to `en` language --- .../Microsoft.PowerShell.Utility/Import-LocalizedData.md | 7 ++++++- .../Microsoft.PowerShell.Utility/Import-LocalizedData.md | 7 ++++++- .../whats-new/What-s-New-in-PowerShell-76.md | 5 ++++- 3 files changed, 16 insertions(+), 3 deletions(-) diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md b/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md index b47db8b287ba..9a30ff172f86 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility -ms.date: 01/19/2023 +ms.date: 03/20/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/import-localizeddata?view=powershell-7.5&WT.mc_id=ps-gethelp schema: 2.0.0 title: Import-LocalizedData @@ -379,6 +379,11 @@ parameter. user messages into the value of the **BindingVariable** parameter in the command. Then, when you display a message from the hashtable in the variable, the localized message is displayed. + Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any + `-` when you don't use the **UICulture** parameter. Therefore, if the command + can't find a localized data for the current culture (`$PSUICulture`), the search falls back to + `en-US` and then to `en` eventually. + For more information, see [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md). diff --git a/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md b/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md index 345327a48e4b..fe7f6b8fa67c 100644 --- a/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md +++ b/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md @@ -2,7 +2,7 @@ external help file: Microsoft.PowerShell.Commands.Utility.dll-Help.xml Locale: en-US Module Name: Microsoft.PowerShell.Utility -ms.date: 01/19/2023 +ms.date: 03/20/2026 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/import-localizeddata?view=powershell-7.6&WT.mc_id=ps-gethelp schema: 2.0.0 title: Import-LocalizedData @@ -379,6 +379,11 @@ parameter. user messages into the value of the **BindingVariable** parameter in the command. Then, when you display a message from the hashtable in the variable, the localized message is displayed. + Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any + `-` when you don't use the **UICulture** parameter. Therefore, if the command + can't find a localized data for the current culture (`$PSUICulture`), the search falls back to + `en-US` and then to `en` eventually. + For more information, see [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md). diff --git a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-76.md b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-76.md index a076d8fd2bca..09b9bdeed9d8 100644 --- a/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-76.md +++ b/reference/docs-conceptual/whats-new/What-s-New-in-PowerShell-76.md @@ -1,7 +1,7 @@ --- title: What's New in PowerShell 7.6 description: New features and changes released in PowerShell 7.6 -ms.date: 02/20/2026 +ms.date: 03/20/2026 --- # What's New in PowerShell 7.6 @@ -89,6 +89,8 @@ PowerShell 7.6 includes the following updated modules: ## Cmdlet improvements +- Add implicit localization fallback to `Import-LocalizedData` ([#19896][19896]) (Thanks + @chrisdent-de!) - Add `-Delimiter` parameter to `Get-Clipboard` ([#26572][26572]) (Thanks @MartinGC94!) - Fix Out-GridView by replacing use of obsolete BinaryFormatter with custom implementation ([#25497][25497]) (Thanks @mawosoft!) @@ -214,6 +216,7 @@ This release includes the following experimental features: [18955]: https://github.com/PowerShell/PowerShell/pull/18955 [19440]: https://github.com/PowerShell/PowerShell/pull/19440 [19830]: https://github.com/PowerShell/PowerShell/pull/19830 +[19896]: https://github.com/PowerShell/PowerShell/pull/19896 [20017]: https://github.com/PowerShell/PowerShell/pull/20017 [20330]: https://github.com/PowerShell/PowerShell/pull/20330 [20340]: https://github.com/PowerShell/PowerShell/pull/20340 From 131ac79e56d11fcfc0fb67139106bfeaa2647de2 Mon Sep 17 00:00:00 2001 From: Sean Wheeler Date: Fri, 20 Mar 2026 10:26:27 -0500 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- .../7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md | 4 ++-- .../7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md b/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md index 9a30ff172f86..8f1f611a3a27 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Import-LocalizedData.md @@ -381,8 +381,8 @@ parameter. Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any `-` when you don't use the **UICulture** parameter. Therefore, if the command - can't find a localized data for the current culture (`$PSUICulture`), the search falls back to - `en-US` and then to `en` eventually. + can't find localized data for the current culture (`$PSUICulture`), the search falls back to + `en-US` and then to `en`. For more information, see [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md). diff --git a/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md b/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md index fe7f6b8fa67c..a1f9b5da57f2 100644 --- a/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md +++ b/reference/7.6/Microsoft.PowerShell.Utility/Import-LocalizedData.md @@ -381,8 +381,8 @@ parameter. Beginning in PowerShell 7.5.5, the cmdlet falls back to `en-US` and then `en` for any `-` when you don't use the **UICulture** parameter. Therefore, if the command - can't find a localized data for the current culture (`$PSUICulture`), the search falls back to - `en-US` and then to `en` eventually. + can't find localized data for the current culture (`$PSUICulture`), the search falls back to + `en-US` and then to `en`. For more information, see [about_Script_Internationalization](../Microsoft.Powershell.Core/About/about_Script_Internationalization.md).