blocks|key|1579651|text|这段代码的原作者是@Scepticalist。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1579652|从powershell控制台运行此命令。它将将当前会话的文化更改为en-US。|1579653|function+Set-CultureWin([System.Globalization.CultureInfo]+$culture)+{+[System.Threading.Thread]::CurrentThread.CurrentUICulture+=+$culture+;+[System.Threading.Thread]::CurrentThread.CurrentCulture+=+$culture+}+;+Set-CultureWin+en-US+;+[system.threading.thread]::currentthread.currentculture|code-block|syntax|javascript|1579654|然后，您必须使用命令Get-NetTCPConnection而不是netstat。有关其使用情况，请参阅https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection?view=win10-ps|offset|length|style|CODE|1579655|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection?view=win10-ps^0|0|0|0|A|K|1G|2N|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$K|10|L|11|M|N]]|9|@$K|12|L|13|1|14]]|A|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Original author of this code is @Scepticalist.

Run this from powershell console. It will change the culture to en-US for current session. 

<pre><code>function Set-CultureWin([System.Globalization.CultureInfo] $culture) { [System.Threading.Thread]::CurrentThread.CurrentUICulture = $culture ; [System.Threading.Thread]::CurrentThread.CurrentCulture = $culture } ; Set-CultureWin en-US ; [system.threading.thread]::currentthread.currentculture
</code></pre>

Then you have to use the command <code>Get-NetTCPConnection</code> Instead of netstat. For its usage see <a href="https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection?view=win10-ps" rel="nofollow noreferrer">https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection?view=win10-ps</a>

blocks|key|1579769|text|(a)+For+外部程序，例如不幸的是，_没有_<代码>E+214方式(据我所知)可以更改UI语言E+115_<代码>E+216会话中的**_：|type|unordered-list-item|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1579770|-+On+Windows+Server+2012+/+Windows+8+and+above,+the+[**`Set-WinUILanguageOverride`**](https://learn.microsoft.com/en-us/powershell/module/international/set-winuilanguageoverride)+**cmdlet**+allows+you+to+(persistently)+**change+the+system-wide+UI+language+for+the+current+user**,+but+that+only+takes+effect+in+_future_+logon+sessions+-+that+is,+**logging+off+and+back+on+or+a+reboot+are+required**.|code-block|syntax|javascript|1579771|-+As+an+aside:+On+Windows+Server+2012+/+Windows+8+and+above,+there+is+also+the+[**`Set-Culture`**](https://learn.microsoft.com/en-us/powershell/module/international/set-culture)+cmdlet,+but+its+**purpose+is**+_**not**_+**to+change+the**+_**UI**_+**culture+(display+language)**,+but+only+culture-specific+**settings+such+as+date,+number,+and+currency+formats**.+It+too+changes+the+setting+_persistently_+for+the+current+user,+but+only+requires+a+new+_session_+(process)+for+the+change+to+take+effect.|1579772|(b)+For+PowerShell命令和+.NET+types，其中E+232E+133是E+234e+135会话内(非持久性)解决方案e+236-假设这些命令是区域性的，并且带有本地化的字符串。|1579773|-+Set+[`[cultureinfo]::CurrentUICulture`](https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentUICulture)+(temporarily)+to+the+desired+culture+name+(use+[`[cultureinfo]::GetCultures('SpecificCultures')`](https://learn.microsoft.com/en-US/dotnet/api/system.globalization.cultureinfo.getcultures)+to+see+all+predefined+ones)+;+e.g.,++`[cultureinfo]::CurrentUICulture+=+'en-US'`|1579774|++++-+Complementarily,+you+may+want+to+set+[`[cultureinfo]::CurrentCulture`](https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentCulture)+(note+the+missing+`UI`+part)+as+well,+which+determines+the+culture-specific+number,+date,+...+formatting.
++++-+In+older+versions+of+PowerShell+/+.NET,+you'll+have+to+set+these+properties+on+[`[System.Threading.Thread]::CurrentThread`](https://learn.microsoft.com/en-US/dotnet/api/System.Threading.Thread.CurrentThread)+instead;+e.g.,|1579775|[System.Threading.Thread]::CurrentThread.CurrentUICulture+=+'en-US'|unstyled|1579776|-+See+the+**bottom+section**+for+**helper+function**+**`Use-Culture`**+that+wraps+this+functionality+for+execution+of+code+with+a+different+culture+temporarily+in+effect;+here's+an+example+call+with+the+culture-sensitive+[`Get-LocalGroupMember`](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/get-localgroupmember)+cmdlet:|1579777|尝试使用"en-US“以外的值，例如"fr-FR”，以查看"ObjectClass“输出列中的本地化#值。使用-区域性en-US+{+Get-LocalGroupMember管理员}|1579778|-+An+**ad+hoc+example**,+if+you+don't+want+to+define+a+helper+function+(only+the+UI+culture+is+changed+here):|1579779|+&{+$prev=cultureinfo::CurrentUICulture+cultureinfo：：CurrentUICulture=‘en’Get-LocalGroupMember+cultureinfo::CurrentUICulture=$prev+}|1579780|警告|1579781|PowerShell+Core+本身是而不是本地化的，截至v7.2.x；但是，下面的解决方案确实适用于带有本地化消息和帮助内容的第三方模块，以及选择与平台API对话的特定于Windows的模块，如Microsoft.PowerShell.LocalAccounts模块，其Get-LocalGroupMember+cmdlet在上面的示例中使用。|1579782|由于[cultureinfo]::CurrentUICulture+Windows+PowerShell中的错误(PowerShell+Core+v6%2B不受影响)，每当命令提示符执行完E+282时，对Windows和+[cultureinfo]::CurrentCulture+的会话中的更改为E+278E+179自动重置E+280<>E+181；然而，对于给定的脚本，更改对整个脚本及其调用仍然有效--参见C+83。|1579783|后退一步：|1579784|我编写了一些使用系统(powershell)命令输出的软件，但没有预见到除了英语以外的语言输出会有所不同。|blockquote|1579785|这正是为什么PowerShell-native+通常值得寻找解决方案而不是调用外部程序的原因|1579786|例如，不必解析(可能是本地化的)+text，netstat.exe**，，PowerShell命令返回_对象_，您可以以与区域性无关的方式可靠地访问它的属性。**|1579787|具体来说，马蒂亚斯·耶森建议将Get-NetTCPConnection视为netstat.exe的一种PowerShell替代方案(可在Windows+2012+/Windows8及更高版本上使用)。|1579788|函数Use-Culture的源代码：|1579789|注意:代码是从这篇受人尊敬的博文中修改而来的；它是设计出来的|1579790|#+Runs+a+script+block+in+the+context+of+the+specified+culture,+without+changing+
#+the+session's+culture+persistently.
#+Handy+for+quickly+testing+the+behavior+of+a+command+in+the+context+of+a+different+culture.
#+Example:+
#+++Use-Culture+fr-FR+{+Get-Date+}
function+Use-Culture
{++++
++param(
++++[Parameter(Mandatory)]+[cultureinfo]+$Culture,
++++[Parameter(Mandatory)]+[scriptblock]+$ScriptBlock
++)
++#+Note:+In+Windows+10,+a+culture-info+object+can+be+created+from+*any*+string.
++#++++++++However,+an+identifier+that+does't+refer+to+a+*predefined*+culture+is+
++#++++++++reflected+in+.LCID+containing+4096+(0x1000)
++if+($Culture.LCID+-eq+4096)+{+Throw+"Unrecognized+culture:+$($Culture.DisplayName)"+}

++#+Save+the+current+culture+/+UI+culture+values.
++$PrevCultures+=+[Threading.Thread]::CurrentThread.CurrentCulture,+[Threading.Thread]::CurrentThread.CurrentUICulture

++try+{
++++#+(Temporarily)+set+the+culture+and+UI+culture+for+the+current+thread.
++++[Threading.Thread]::CurrentThread.CurrentCulture+=+[Threading.Thread]::CurrentThread.CurrentUICulture+=+$Culture

++++#+Now+invoke+the+given+code.
++++&+$ScriptBlock

++}++++
++finally+{
++++#+Restore+the+previous+culture+/+UI+culture+values.
++++[Threading.Thread]::CurrentThread.CurrentCulture+=+$PrevCultures[0]
++++[Threading.Thread]::CurrentThread.CurrentUICulture+=+$PrevCultures[1]
++}
}|1579791|entityMap|0|LINK|mutability|MUTABLE|url|https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/|1|https://stackoverflow.com/users/712649/mathias-r-jessen|2|https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection|3|https://rkeithhill.wordpress.com/2009/10/21/windows-powershell-2-0-string-localization/^0|4|3|8|1S|1D|5|0|0|0|0|7|8|D|M|25|Z|A|1A|A|1X|5|0|0|0|0|1V|0|1V|0|0|A2|0|0|2J|0|0|31|0|0|3O|0|0|2|0|0|F|G|4D|2Q|Y|3S|K|2Q|Y|0|0|0|30|31|T|3V|1Y|2|V|2K|G|31|T|3V|1Y|0|0|5|0|5|0|0|1H|0|1H|0|0|N|O|M|0|N|O|M|0|0|29|0|29|0|0|2S|0|2S|5|7|1|F|K|2|0|0|I|0|I|0|0|U|0|U|7|9|3|0|0|11U|0^^$0|@$1|2|3|4|5|6|7|25|8|@$9|26|A|27|B|C]|$9|28|A|29|B|C]|$9|2A|A|2B|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|2C|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|I|7|2D|8|@]|E|@]|F|$J|K]]|$1|N|3|O|5|6|7|2E|8|@$9|2F|A|2G|B|C]|$9|2H|A|2I|B|C]|$9|2J|A|2K|B|C]|$9|2L|A|2M|B|D]|$9|2N|A|2O|B|D]|$9|2P|A|2Q|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|I|7|2R|8|@]|E|@]|F|$J|K]]|$1|R|3|S|5|I|7|2S|8|@]|E|@]|F|$J|K]]|$1|T|3|U|5|V|7|2T|8|@$9|2U|A|2V|B|C]|$9|2W|A|2X|B|D]]|E|@]|F|$]]|$1|W|3|X|5|I|7|2Y|8|@$9|2Z|A|30|B|C]]|E|@]|F|$J|K]]|$1|Y|3|Z|5|V|7|31|8|@$9|32|A|33|B|C]]|E|@]|F|$]]|$1|10|3|11|5|I|7|34|8|@$9|35|A|36|B|C]]|E|@]|F|$J|K]]|$1|12|3|13|5|V|7|37|8|@$9|38|A|39|B|C]]|E|@]|F|$]]|$1|14|3|15|5|V|7|3A|8|@$9|3B|A|3C|B|C]]|E|@]|F|$]]|$1|16|3|17|5|6|7|3D|8|@$9|3E|A|3F|B|C]|$9|3G|A|3H|B|C]|$9|3I|A|3J|B|D]|$9|3K|A|3L|B|D]]|E|@$9|3M|A|3N|1|3O]]|F|$]]|$1|18|3|19|5|6|7|3P|8|@$9|3Q|A|3R|B|C]|$9|3S|A|3T|B|C]|$9|3U|A|3V|B|C]|$9|3W|A|3X|B|D]|$9|3Y|A|3Z|B|D]|$9|40|A|41|B|D]|$9|42|A|43|B|D]]|E|@]|F|$]]|$1|1A|3|1B|5|V|7|44|8|@$9|45|A|46|B|C]|$9|47|A|48|B|D]]|E|@]|F|$]]|$1|1C|3|1D|5|1E|7|49|8|@$9|4A|A|4B|B|C]|$9|4C|A|4D|B|D]]|E|@]|F|$]]|$1|1F|3|1G|5|V|7|4E|8|@$9|4F|A|4G|B|C]|$9|4H|A|4I|B|C]|$9|4J|A|4K|B|D]|$9|4L|A|4M|B|D]]|E|@]|F|$]]|$1|1H|3|1I|5|V|7|4N|8|@$9|4O|A|4P|B|C]|$9|4Q|A|4R|B|D]]|E|@]|F|$]]|$1|1J|3|1K|5|V|7|4S|8|@$9|4T|A|4U|B|C]|$9|4V|A|4W|B|D]]|E|@$9|4X|A|4Y|1|4Z]|$9|50|A|51|1|52]]|F|$]]|$1|1L|3|1M|5|V|7|53|8|@$9|54|A|55|B|C]|$9|56|A|57|B|D]]|E|@]|F|$]]|$1|1N|3|1O|5|V|7|58|8|@$9|59|A|5A|B|C]|$9|5B|A|5C|B|D]]|E|@$9|5D|A|5E|1|5F]]|F|$]]|$1|1P|3|1Q|5|I|7|5G|8|@$9|5H|A|5I|B|C]]|E|@]|F|$J|K]]|$1|1R|3|-4|5|V|7|5J|8|@]|E|@]|F|$]]]|1S|$1T|$5|1U|1V|1W|F|$1X|1Y]]|1Z|$5|1U|1V|1W|F|$1X|20]]|21|$5|1U|1V|1W|F|$1X|22]]|23|$5|1U|1V|1W|F|$1X|24]]]]

<ul>
<li>(a) For external programs such as <code>netstat.exe</code>, there is unfortunately no way (that I know of) to change the UI language in-session:
<ul>
<li>On Windows Server 2012 / Windows 8 and above, the <a href="https://learn.microsoft.com/en-us/powershell/module/international/set-winuilanguageoverride" rel="nofollow noreferrer"><code>Set-WinUILanguageOverride</code></a> cmdlet allows you to (persistently) change the system-wide UI language for the current user, but that only takes effect in future logon sessions - that is, logging off and back on or a reboot are required.
</li>
<li>As an aside: On Windows Server 2012 / Windows 8 and above, there is also the <a href="https://learn.microsoft.com/en-us/powershell/module/international/set-culture" rel="nofollow noreferrer"><code>Set-Culture</code></a> cmdlet, but its purpose is not to change the UI culture (display language), but only culture-specific settings such as date, number, and currency formats. It too changes the setting persistently for the current user, but only requires a new session (process) for the change to take effect.
</li>
</ul>
</li>
<li>(b) For PowerShell commands and .NET types, there is an in-session (non-persistent) solution - assuming the commands are culture-aware and come with localized strings:
<ul>
<li>Set <a href="https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentUICulture" rel="nofollow noreferrer"><code>[cultureinfo]::CurrentUICulture</code></a> (temporarily) to the desired culture name (use <a href="https://learn.microsoft.com/en-US/dotnet/api/system.globalization.cultureinfo.getcultures" rel="nofollow noreferrer"><code>[cultureinfo]::GetCultures('SpecificCultures')</code></a> to see all predefined ones) ; e.g., <code>[cultureinfo]::CurrentUICulture = 'en-US'</code>
<ul>
<li>Complementarily, you may want to set <a href="https://learn.microsoft.com/en-US/dotnet/api/System.Globalization.CultureInfo.CurrentCulture" rel="nofollow noreferrer"><code>[cultureinfo]::CurrentCulture</code></a> (note the missing <code>UI</code> part) as well, which determines the culture-specific number, date, ... formatting.</li>
<li>In older versions of PowerShell / .NET, you'll have to set these properties on <a href="https://learn.microsoft.com/en-US/dotnet/api/System.Threading.Thread.CurrentThread" rel="nofollow noreferrer"><code>[System.Threading.Thread]::CurrentThread</code></a> instead; e.g., 
<code>[System.Threading.Thread]::CurrentThread.CurrentUICulture = 'en-US'</code></li>
</ul>
</li>
<li>See the bottom section for helper function <code>Use-Culture</code> that wraps this functionality for execution of code with a different culture temporarily in effect; here's an example call
with the culture-sensitive <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/get-localgroupmember" rel="nofollow noreferrer"><code>Get-LocalGroupMember</code></a> cmdlet:
<pre class="lang-sh prettyprint-override"><code># Try with values other than &quot;en-US&quot;, e.g. &quot;fr-FR&quot; to see localized
# values in the &quot;ObjectClass&quot; output column.
Use-Culture en-US { Get-LocalGroupMember Administrators } 
</code></pre>
</li>
<li>An ad hoc example, if you don't want to define a helper function (only the UI culture is changed here):
<pre class="lang-sh prettyprint-override"><code>&amp; {
 $prev=[cultureinfo]::CurrentUICulture
 [cultureinfo]::CurrentUICulture='en-US'
 Get-LocalGroupMember Administrators
 [cultureinfo]::CurrentUICulture=$prev
}
</code></pre>
</li>
</ul>
</li>
</ul>
Caveats:
<ul>
<li>PowerShell [Core] itself is not localized yet, as of v7.2.x; progress is being tracked in <a href="https://github.com/PowerShell/PowerShell/issues/666" rel="nofollow noreferrer">GitHub issue #666</a>; however, the solution below does work with third-party modules that ship with localized messages and help content, as well as select Windows-specific modules that talk to platform APIs, such as the <a href="https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.localaccounts/" rel="nofollow noreferrer"><code>Microsoft.PowerShell.LocalAccounts</code></a> module, whose <code>Get-LocalGroupMember</code> cmdlet was used in the example above.
</li>
<li>Due to a bug in Windows PowerShell (PowerShell [Core] v6+ is not affected), in-session changes to <code>[cultureinfo]::CurrentUICulture</code> and <code>[cultureinfo]::CurrentCulture</code> are automatically reset at the command prompt, whenever a command finishes executing; however, for a given script the changes remain in effect for the entire script and its callees - see <a href="https://stackoverflow.com/a/56922526/45375">this answer</a>.
</li>
</ul>
<hr />
Taking a step back:
<blockquote>
I wrote some software that uses the output of system (powershell) commands, but did not foresee that the output would be different for languages other than English.
</blockquote>
This is precisely why it's generally worth looking for PowerShell-native solutions as opposed to calling external programs:
Instead of having to parse - possibly localized - text, as with <code>netstat.exe</code>, for instance, PowerShell commands return objects whose properties you can robustly access in a culture-independent fashion.
Specifically, <a href="https://stackoverflow.com/users/712649/mathias-r-jessen">Mathias R. Jessen</a> suggests looking at <a href="https://learn.microsoft.com/en-us/powershell/module/nettcpip/get-nettcpconnection" rel="nofollow noreferrer"><code>Get-NetTCPConnection</code></a> as a PowerShell alternative to <code>netstat.exe</code> (available on Windows Server 2012 / Windows 8 and above).
<hr />
<h3>Function <code>Use-Culture</code>'s source code:</h3>
Note: The code was gratefully adapted from <a href="https://rkeithhill.wordpress.com/2009/10/21/windows-powershell-2-0-string-localization/" rel="nofollow noreferrer">this venerable blog post</a>; it is designed
<pre class="lang-sh prettyprint-override"><code># Runs a script block in the context of the specified culture, without changing 
# the session's culture persistently.
# Handy for quickly testing the behavior of a command in the context of a different culture.
# Example: 
# Use-Culture fr-FR { Get-Date }
function Use-Culture
{ 
 param(
 [Parameter(Mandatory)] [cultureinfo] $Culture,
 [Parameter(Mandatory)] [scriptblock] $ScriptBlock
 )
 # Note: In Windows 10, a culture-info object can be created from *any* string.
 # However, an identifier that does't refer to a *predefined* culture is 
 # reflected in .LCID containing 4096 (0x1000)
 if ($Culture.LCID -eq 4096) { Throw &quot;Unrecognized culture: $($Culture.DisplayName)&quot; }

 # Save the current culture / UI culture values.
 $PrevCultures = [Threading.Thread]::CurrentThread.CurrentCulture, [Threading.Thread]::CurrentThread.CurrentUICulture

 try {
 # (Temporarily) set the culture and UI culture for the current thread.
 [Threading.Thread]::CurrentThread.CurrentCulture = [Threading.Thread]::CurrentThread.CurrentUICulture = $Culture

 # Now invoke the given code.
 &amp; $ScriptBlock

 } 
 finally {
 # Restore the previous culture / UI culture values.
 [Threading.Thread]::CurrentThread.CurrentCulture = $PrevCultures[0]
 [Threading.Thread]::CurrentThread.CurrentUICulture = $PrevCultures[1]
 }
}
</code></pre>

I wrote some software that uses the output of system (powershell) commands, but did not foresee that the output would be different for languages other than English. 

Is there a way to temporarily change the language in Powershell to English for just that one, single powershell session?

<h3>Notes</h3>

<ul>
<li>In case it is of significance, the particular powershell code I wish to run is <code>netstat -n -a</code></li>
<li>I have come across some ways to change powershell language (e.g. <a href="https://social.technet.microsoft.com/Forums/exchange/en-US/6ed8f2d9-082a-4c86-8066-e9b2391f5dff/how-to-change-language-in-powershell-to-english?forum=winserverpowershell" rel="noreferrer">here</a>, <a href="https://community.spiceworks.com/topic/560456-how-to-change-powershell-script-errors-to-english" rel="noreferrer">here</a>). But I want to be careful not to change it permanently! (that would be bad)</li>
</ul>

Temporarily change powershell language to English?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我编写了一些使用系统(powershell)命令输出的软件，但没有预见到除了英语以外的语言输出会有所不同。是否有一种方法可以暂时将Powershell中的语言更改为英语，只用于这一次，即单个powershell会话备注如果有意义，我希望运行的特定powershell代码是netstat -n -a。我遇到了一些改变po...

问暂时将powershell语言改为英语？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问暂时将powershell语言改为英语？EN