https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649
--- Comment #12 from Guy Harris <ghar...@sonic.net> ---
And then there's
https://stackoverflow.com/a/11906745
which says
And I think a simple pipe will kill your new and shiny unicode text. Let's
say your exe named a.exe. I'm pretty sure, that a.exe | more will NOT display
unicode text.
So complete UTF-8-ification of Windows, to the extent that UTF-8-oriented code
in applications and libraries for UN*X can be made to work .on Windows without
too much pain, is a big project, incomplete as of now, and will probably end up
only working completely if every code page is set to 65001.
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
