https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649
--- Comment #13 from Guy Harris <ghar...@sonic.net> ---
With a recently-updated Windows 10 (Version 2004, OS Build 19041.329),
compiling with a recently-updated VS 2019 (Microsoft (R) C/C++ Optimizing
Compiler Version 19.26.28806 for x64), I get:
C:\ ?C in macOS → ^C elsewhere
with the console code page set to 437, so they *did* fix the "lower ASCII"
problem (as per the right arrow showing up), but they still have the "Unicode
characters not in the console code page" problem (as per the "place of
interest" marker mapping to a question mark), and I get:
C:\ ⌘C in macOS → ^C elsewhere
with the console code page set to 65001, so it Just Works *if* you're using
UTF-8 as the console code path.
And, as for piping to more, if the console code page is 437 and I pipe the
output of utf8test to more, I get
C:\ ⌘C in macOS → ^C elsewhere
which is completely mangled (as nobody's translating UTF-8 to the local code
page, and more has no clue that it's getting UTF-8 on the standard input. (And
changing utf8test to put a UTF-8 version of the byte-order mark does *not* make
a difference, so more doesn't appear to be checking for it.)
--
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
