Tested in Windows 7 (Japanese).
Import-Csvdoes not have
-Encodingoption in PowerShell 2.0.
- There are no option for UTF-32BE in PowerShell 2.0. (note: PowerShell ISE can handle UTF-32BE Files)
Import-Csvdoes not support
OEM, and without
-Encodingoption are the same.
- File in UTF-16 with BOM can be read even if
-Encodingoption is wrong
- UTF-32BE with BOM could be misdetermined to UTF-16BE (because starting bytes are FEFF)