blocks|key|722057|text|使用.NET的UTF8Encoding类并将$False传递给构造函数似乎是可行的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|722058|$MyRawString+=+Get-Content+-Raw+$MyPath
$Utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding+$False
[System.IO.File]::WriteAllLines($MyPath,+$MyRawString,+$Utf8NoBomEncoding)|code-block|syntax|javascript|722059|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.text.utf8encoding.aspx^0|7|C|M|6|7|C|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

Using .NET's <a href="http://msdn.microsoft.com/en-us/library/system.text.utf8encoding.aspx" rel="noreferrer"><code>UTF8Encoding</code></a> class and passing <code>$False</code> to the constructor seems to work:

<pre><code>$MyRawString = Get-Content -Raw $MyPath
$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding $False
[System.IO.File]::WriteAllLines($MyPath, $MyRawString, $Utf8NoBomEncoding)
</code></pre>

blocks|key|937901|text|此脚本将DIRECTORY1中的所有.txt文件转换为不带物料清单的UTF-8格式，并将它们输出到DIRECTORY2|type|unstyled|depth|inlineStyleRanges|entityRanges|data|937902|foreach+($i+in+ls+-name+DIRECTORY1\*.txt)
{
++++$file_content+=+Get-Content+"DIRECTORY1\$i";
++++[System.IO.File]::WriteAllLines("DIRECTORY2\$i",+$file_content);
}|code-block|syntax|javascript|937903|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This script will convert, to UTF-8 without BOM, all .txt files in DIRECTORY1 and output them to DIRECTORY2

<pre><code>foreach ($i in ls -name DIRECTORY1\*.txt)
{
 $file_content = Get-Content "DIRECTORY1\$i";
 [System.IO.File]::WriteAllLines("DIRECTORY2\$i", $file_content);
}
</code></pre>

blocks|key|937973|text|这个方法适用于我(使用"Default“而不是"UTF8")：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|937974|$MyFile+=+Get-Content+$MyPath
$MyFile+%7C+Out-File+-Encoding+"Default"+$MyPath|code-block|syntax|javascript|937975|结果是没有BOM的ASCII。|937976|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This one works for me (use "Default" instead of "UTF8"):

<pre><code>$MyFile = Get-Content $MyPath
$MyFile | Out-File -Encoding "Default" $MyPath
</code></pre>

The result is ASCII without BOM.

blocks|key|938021|text|可以使用下面的代码在没有物料清单的情况下获取UTF8|type|unstyled|depth|inlineStyleRanges|entityRanges|data|938022|$MyFile+%7C+Out-File+-Encoding+ASCII|code-block|syntax|javascript|938023|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Could use below to get UTF8 without BOM

<pre><code>$MyFile | Out-File -Encoding ASCII
</code></pre>

blocks|key|938124|text|按扩展名将多个文件更改为不带BOM的UTF-8：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|938125|$Utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding($False)
foreach($i+in+ls+-recurse+-filter+"*.java")+{
++++$MyFile+=+Get-Content+$i.fullname+
++++[System.IO.File]::WriteAllLines($i.fullname,+$MyFile,+$Utf8NoBomEncoding)
}|code-block|syntax|javascript|938126|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Change multiple files by extension to UTF-8 without BOM:

<pre><code>$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding($False)
foreach($i in ls -recurse -filter "*.java") {
 $MyFile = Get-Content $i.fullname 
 [System.IO.File]::WriteAllLines($i.fullname, $MyFile, $Utf8NoBomEncoding)
}
</code></pre>

blocks|key|938163|text|我认为这不是UTF，但我只是找到了一个非常简单的解决方案，似乎是有效的…|type|unstyled|depth|inlineStyleRanges|entityRanges|data|938164|Get-Content+path/to/file.ext+%7C+out-file+-encoding+ASCII+targetFile.ext|code-block|syntax|javascript|938165|对我来说，这导致了一个没有bom文件的utf-8文件，而不管是什么源格式。|938166|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I figured this wouldn't be UTF, but I just found a pretty simple solution that seems to work...

<pre><code>Get-Content path/to/file.ext | out-file -encoding ASCII targetFile.ext
</code></pre>

For me this results in a utf-8 without bom file regardless of the source format.

blocks|key|722411|text|++++[System.IO.FileInfo]+$file+=+Get-Item+-Path+$FilePath+
++++$sequenceBOM+=+New-Object+System.Byte[]+3+
++++$reader+=+$file.OpenRead()+
++++$bytesRead+=+$reader.Read($sequenceBOM,+0,+3)+
++++$reader.Dispose()+
++++#A+UTF-8%2BBOM+string+will+start+with+the+three+following+bytes.+Hex:+0xEF0xBB0xBF,+Decimal:+239+187+191+
++++if+($bytesRead+-eq+3+-and+$sequenceBOM[0]+-eq+239+-and+$sequenceBOM[1]+-eq+187+-and+$sequenceBOM[2]+-eq+191)+
++++{+
++++++++$utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding($False)+
++++++++[System.IO.File]::WriteAllLines($FilePath,+(Get-Content+$FilePath),+$utf8NoBomEncoding)+
++++++++Write-Host+"Remove+UTF-8+BOM+successfully"+
++++}+
++++Else+
++++{+
++++++++Write-Warning+"Not+UTF-8+BOM+file"+
++++}++|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|722412|源How+to+remove+UTF8+Byte+Order+Mark+(BOM)+from+a+file+using+PowerShell|unstyled|offset|length|722413|entityMap|0|LINK|mutability|MUTABLE|url|https://gallery.technet.microsoft.com/How-to-remove-UTF8-Byte-a66fc0b2^0|0|1|1X|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code> [System.IO.FileInfo] $file = Get-Item -Path $FilePath 
 $sequenceBOM = New-Object System.Byte[] 3 
 $reader = $file.OpenRead() 
 $bytesRead = $reader.Read($sequenceBOM, 0, 3) 
 $reader.Dispose() 
 #A UTF-8+BOM string will start with the three following bytes. Hex: 0xEF0xBB0xBF, Decimal: 239 187 191 
 if ($bytesRead -eq 3 -and $sequenceBOM[0] -eq 239 -and $sequenceBOM[1] -eq 187 -and $sequenceBOM[2] -eq 191) 
 { 
 $utf8NoBomEncoding = New-Object System.Text.UTF8Encoding($False) 
 [System.IO.File]::WriteAllLines($FilePath, (Get-Content $FilePath), $utf8NoBomEncoding) 
 Write-Host "Remove UTF-8 BOM successfully" 
 } 
 Else 
 { 
 Write-Warning "Not UTF-8 BOM file" 
 } 
</code></pre>

Source <a href="https://gallery.technet.microsoft.com/How-to-remove-UTF8-Byte-a66fc0b2" rel="nofollow noreferrer">How to remove UTF8 Byte Order Mark (BOM) from a file using PowerShell</a>

blocks|key|722500|text|如果要使用[System.IO.File]::WriteAllLines()，则应将第二个参数转换为String[]+(如果$MyFile的类型为Object[])，并使用$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($MyPath)指定绝对路径，如：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|722501|$Utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding+$False
Get-ChildItem+%7C+ConvertTo-Csv+%7C+Set-Variable+MyFile
[System.IO.File]::WriteAllLines($ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($MyPath),+[String[]]$MyFile,+$Utf8NoBomEncoding)|code-block|syntax|javascript|722502|如果您想使用[System.IO.File]::WriteAllText()，有时您应该将第二个参数通过管道传递到%7C+Out-String+%7C中，以便显式地将CRLF添加到每行的末尾(特别是当您将它们与ConvertTo-Csv一起使用时)：|722503|$Utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding+$False
Get-ChildItem+%7C+ConvertTo-Csv+%7C+Out-String+%7C+Set-Variable+tmp
[System.IO.File]::WriteAllText("/absolute/path/to/foobar.csv",+$tmp,+$Utf8NoBomEncoding)|722504|或者，您可以在Set-Content+-Encoding+Byte中使用[Text.Encoding]::UTF8.GetBytes()|722505|$Utf8NoBomEncoding+=+New-Object+System.Text.UTF8Encoding+$False
Get-ChildItem+%7C+ConvertTo-Csv+%7C+Out-String+%7C+%25+{+[Text.Encoding]::UTF8.GetBytes($_)+}+%7C+Set-Content+-Encoding+Byte+-Path+"/absolute/path/to/foobar.csv"|722506|请参阅：How+to+write+result+of+ConvertTo-Csv+to+a+file+in+UTF-8+without+BOM|722507|entityMap|0|LINK|mutability|MUTABLE|url|http://satob.hatenablog.com/entry/2017/05/11/001905^0|5|X|1E|8|1Q|7|21|8|2E|28|0|0|6|W|1L|E|2T|D|0|0|7|Q|10|W|0|0|4|1V|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1L|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1M|8|@$9|1N|A|1O|B|C]|$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1R|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1S|8|@]|D|@$9|1T|A|1U|1|1V]]|E|$]]|$1|U|3|-4|5|6|7|1W|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

If you want to use <code>[System.IO.File]::WriteAllLines()</code>, you should cast second parameter to <code>String[]</code> (if the type of <code>$MyFile</code> is <code>Object[]</code>), and also specify absolute path with <code>$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($MyPath)</code>, like:

<pre><code>$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding $False
Get-ChildItem | ConvertTo-Csv | Set-Variable MyFile
[System.IO.File]::WriteAllLines($ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($MyPath), [String[]]$MyFile, $Utf8NoBomEncoding)
</code></pre>

If you want to use <code>[System.IO.File]::WriteAllText()</code>, sometimes you should pipe the second parameter into <code>| Out-String |</code> to add CRLFs to the end of each line explictly (Especially when you use them with <code>ConvertTo-Csv</code>):

<pre><code>$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding $False
Get-ChildItem | ConvertTo-Csv | Out-String | Set-Variable tmp
[System.IO.File]::WriteAllText("/absolute/path/to/foobar.csv", $tmp, $Utf8NoBomEncoding)
</code></pre>

Or you can use <code>[Text.Encoding]::UTF8.GetBytes()</code> with <code>Set-Content -Encoding Byte</code>:

<pre><code>$Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding $False
Get-ChildItem | ConvertTo-Csv | Out-String | % { [Text.Encoding]::UTF8.GetBytes($_) } | Set-Content -Encoding Byte -Path "/absolute/path/to/foobar.csv"
</code></pre>

see: <a href="http://satob.hatenablog.com/entry/2017/05/11/001905" rel="nofollow noreferrer">How to write result of ConvertTo-Csv to a file in UTF-8 without BOM</a>

blocks|key|938294|text|当使用Set-Content而不是Out-File时，您可以指定编码Byte，它可用于将字节数组写入文件。这与不发出物料清单的自定义UTF8编码相结合，提供了所需的结果：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|938295|#+This+variable+can+be+reused
$utf8+=+New-Object+System.Text.UTF8Encoding+$false

$MyFile+=+Get-Content+$MyPath+-Raw
Set-Content+-Value+$utf8.GetBytes($MyFile)+-Encoding+Byte+-Path+$MyPath|code-block|syntax|javascript|938296|与使用[IO.File]::WriteAllLines()或类似的不同之处在于，它应该可以很好地处理任何类型的项目和路径，而不仅仅是实际的文件路径。|938297|entityMap^0|3|B|H|8|Y|4|0|0|3|Q|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

When using <code>Set-Content</code> instead of <code>Out-File</code>, you can specify the encoding <code>Byte</code>, which can be used to write a byte array to a file. This in combination with a custom UTF8 encoding which does not emit the BOM gives the desired result:

<pre><code># This variable can be reused
$utf8 = New-Object System.Text.UTF8Encoding $false

$MyFile = Get-Content $MyPath -Raw
Set-Content -Value $utf8.GetBytes($MyFile) -Encoding Byte -Path $MyPath
</code></pre>

The difference to using <code>[IO.File]::WriteAllLines()</code> or similar is that it should work fine with any type of item and path, not only actual file paths.

blocks|key|722616|text|对于PowerShell+5.1，启用此设置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|722617|控制面板，区域，管理，更改系统区域设置，使用Unicode+UTF-8提供全球语言支持|722618|然后在PowerShell中输入以下内容：|722619|$PSDefaultParameterValues['*:Encoding']+=+'Default'|code-block|syntax|javascript|722620|或者，您可以升级到PowerShell+6或更高版本。|722621|https://github.com/PowerShell/PowerShell|offset|length|722622|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|14|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|10|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|12|8|@]|9|@$O|13|P|14|1|15]]|A|$]]|$1|Q|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|N]]]]

For PowerShell 5.1, enable this setting:
Control Panel, Region, Administrative, Change system locale, Use Unicode UTF-8
for worldwide language support
Then enter this into PowerShell:
<pre><code>$PSDefaultParameterValues['*:Encoding'] = 'Default'
</code></pre>
Alternatively, you can upgrade to PowerShell 6 or higher.
<a href="https://github.com/PowerShell/PowerShell" rel="nofollow noreferrer">https://github.com/PowerShell/PowerShell</a>

blocks|key|722662|text|我在PowerShell中遇到了同样的错误，并使用此隔离并修复了它|type|unstyled|depth|inlineStyleRanges|entityRanges|data|722663|$PSDefaultParameterValues['*:Encoding']+=+'utf8'|code-block|syntax|javascript|722664|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I have the same error in the PowerShell and used this isolation and fixed it
<pre><code>$PSDefaultParameterValues['*:Encoding'] = 'utf8'
</code></pre>

<code>Out-File</code> seems to force the BOM when using UTF-8:
<pre><code>$MyFile = Get-Content $MyPath
$MyFile | Out-File -Encoding &quot;UTF8&quot; $MyPath
</code></pre>
How can I write a file in UTF-8 with no BOM using PowerShell?
<h3>Update 2021</h3>
PowerShell has changed a bit since I wrote this question 10 years ago. Check multiple answers below, they have a lot of good information!

Using PowerShell to write a file in UTF-8 without the BOM

在使用UTF-8时，Out-File似乎会强制执行物料清单：$MyFile = Get-Content $MyPath$MyFile | Out-File -Encoding "UTF8" $MyPath如何使用PowerShell在没有BOM的情况下以UTF-8格式编写文件？更新2021自从我10年前写了这个问题以来...

问使用PowerShell在无BOM的UTF8中写入文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PowerShell在无BOM的UTF8中写入文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用PowerShell在无BOM的UTF8中写入文件
EN