Activity for TeeW
-
TeeW released /bin/x86/teew_v1.1_x86.zip
-
-
-
Steffen modified a comment on a wiki page
Why is the output always written UTF-16-encoded? The Windows console works with an OEM code page. Redirected to a file and opened in a Windows application (such as Notepad) non-ASCII characters would be interpreted using an ANSI code page which corrupts the text that shows up in the window. UTF-16 is an encoding that supports Unicode entirely and it is the preferred encoding for Unicode on Windows. That's the reason why I picked it up as the default for TeeW.
-
Why is the output always written UTF-16-encoded? The Windows console works with a OEM code page. Redirected to a file and opened in a Windows application (such as Notepad) non-ASCII characters would be interpreted using an ANSI code page which corrupts the text that shows up in the window. UTF-16 is an encoding that supports Unicode entirely and it is the preferred encoding for Unicode on Windows. That's the reason why I picked it up as the default for TeeW.
-
UTF-8 support is a feature? Unlike other operating systems, UTF-8 is badly supported on Windows. On the other hand UTF-8 is one of the code pages you are able to set (using CHCP 65001) in order to support Unicode for the standard input. Unfortunately it's still buggy. For more information about this bug see https://www.dostips.com/forum/viewtopic.php?f=3&t=9017 TeeW works around this bug for the text read from standard input.
-
What is TeeW for? "Tee" has the same meaning as the tee command in *nixoid shells. The "W" is for Windows. The tee is the pronunciation of the letter T which illustrates how the utility works. The horizontal bar is for the standard input that gets passed through to the standard output of the console window. The vertical bar is like a bypass. That is, the input stream will be duplicated and written to one or more files in parallel.
-
-
-
-
-
-
-
-
1
