mirror of
https://github.com/ScoopInstaller/Main.git
synced 2025-11-08 09:41:20 +00:00
0ef4806272
* change method of generating gow.bat to generate a normal ASCII character file .# DISCUSSION At the PowerShell command line, using `echo STRING > FILE` will generate a UTF-8-BOM or UTF-16-BOM encoded file. But, CMD interprets files as using the 128-character ASCII character set (character codes 0 to 127). CMD will tolerate files using the full 256 character "extended-ASCII" set (or even larger dual-byte character sets). But, in this circumstance, interpretation/display is dependent on the currently selected code page. It's best to stick to pure ASCII files if at all possible. Using `STRING | Set-Content FILE` instead creates the correct ASCII character file. NOTE: ASCII (not "extended-ASCII") and UTF-8 (non-BOM) encoded files are exactly equivalent. ref: [Unicode UTF and BOM] http://www.unicode.org/faq/utf_bom.html @@ https://archive.is/TKnyk ref: [Unicode and NET] http://csharpindepth.com/Articles/General/Unicode.aspx @@ https://archive.is/czs89