15.3. Content Encoding
Text is an interesting thing. Computers were invented by people who spoke English, and the first text formats, like the American Standard Code for Information Interchange (ASCII), used only a single byte to represent a character. This put a limit on the number of characters that can be represented. The encoding is suitable to represent the Latin alphabet, but fails completely for other character sets like Cyrillic, Hebrew, Arabic, Chinese, Japanese, Korean, and so on. That is why the Unicode Consortium folks have come up with a standard way of encoding text that should be able to accommodate all character sets.
The PowerShell cmdlets like Get-Content and Set-Content support specifying the encoding that should be used when ...
Get Pro Windows PowerShell now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
