hlk123: -------------------------------------------------------------------------------- How about using the format UTF-16 BE--------------------------------------------------------------------------------
Internally Windows use UTF-16 LE. If you want to use a unicode encoding I suggest you to use this because BE is only used in some special applications. Also UTF-8 is a good choice. It's used in websites and *nixoid operating systems (Unix, Linux, Mac OS, Android). The drawback is that these encodings need more space (as Jan already said). UTF-16 uses 2 bytes in general and if there are characters that can't be expressed with 2 bytes it uses surrogate pairs (4 bytes) which may happen for some Chinese characters in your case. UTF-8 uses 1 byte for ASCII and up to 4 bytes depending on what non-ASCII character has to be expressed. However, a lot of programs still don't understand unicode. E.g. Windows scripts must not be encoded in UTF-16 (e.g. Batch) or UTF-8 (e.g. Batch or VBScript) because the interpreters don't expect it and fail. hlk123: -------------------------------------------------------------------------------- dos.tips ... I thought DOS belongs to previous century ... :-)-------------------------------------------------------------------------------- DosTips.com is about Windows Batch. The name is misleading but a lot of people (including you) call the console window still DOS-Box. But you're almost right. Batch will die and Powershell is the future. Steffen -- <https://forum.pspad.com/read.php?2,69681,69714> PSPad freeware editor https://www.pspad.com
