[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 Jaap Keuter changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|---

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #18 from Gerrit Code Review --- Change 37560 merged by Gerald Combs: Windows: Set our locale to ".UTF-8". https://code.wireshark.org/review/37560 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #17 from Gerald Combs --- I modified the test program to print the console output code page and ANSI CP (which is used by setlocale(..., "")), add MIDDLE DOTS to the test message, and to print the test message with no code

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #15 from Gerald Combs --- Created attachment 17851 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17851=edit Test program batch wrapper -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #16 from Gerald Combs --- Created attachment 17852 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17852=edit Test program + wrapper output on Server 2019 -- You are receiving this mail because: You are watching

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #14 from Gerald Combs --- Created attachment 17850 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17850=edit Modified test program -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #13 from Guy Harris --- 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

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #12 from Guy Harris --- 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

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #11 from Guy Harris --- (In reply to Guy Harris from comment #10) > * if the "textmode" is either __crt_lowio_text_mode::utf16le or > __crt_lowio_text_mode::utf8, the buffer appears to be treated as UTF-16LE in > *either*

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #10 from Guy Harris --- I was testing some stuff with the simple program #define UTF8_PLACE_OF_INTEREST_SIGN "\xe2\x8c\x98" /* 8984 / 0x2318 */ #define UTF8_RIGHTWARDS_ARROW "\xe2\x86\x92" /* 8594 /

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #9 from Gerald Combs --- (In reply to Guy Harris from comment #7) > In older versions you could kinda sorta do that but you might not like the > results. Is that an issue if a (careful) program makes that its locale? >

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #8 from Guy Harris --- (In reply to Guy Harris from comment #7) > (In reply to Gerald Combs from comment #5) > > Sorry this is kind of long, but the rabbit hole went lots of places. > > Bear in mind that one of the big

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #7 from Guy Harris --- (In reply to Gerald Combs from comment #5) > Sorry this is kind of long, but the rabbit hole went lots of places. Bear in mind that one of the big original proponents of Unicode had a line of 16-bit

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #6 from Gerrit Code Review --- Change 37560 had a related patch set uploaded by Gerald Combs: Windows: Set our locale to ".65001". https://code.wireshark.org/review/37560 -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #5 from Gerald Combs --- Sorry this is kind of long, but the rabbit hole went lots of places. = What is tshark doing? As Pascal notes in comment #4, packet data is printed via epan/print_stream.c:print_line_color_text, which

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 Pascal Quantin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC|

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #3 from Christopher Maynard --- "chcp 65001" doesn't help either; you just get different garbled output than when using the previous 437 code page regardless of shell, namely: 1 0x0002

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #2 from Christopher Maynard --- (In reply to Jaap Keuter from comment #1) > That looks like an encoding issue, the string is using 'middle dots' > (https://codepoints.net/U+00B7). Seems like a regression since this was

[Wireshark-bugs] [Bug 16649] tcp.flags.str doesn't display the string properly in either a powershell or cmd command prompt.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16649 --- Comment #1 from Jaap Keuter --- That looks like an encoding issue, the string is using 'middle dots' (https://codepoints.net/U+00B7). -- You are receiving this mail because: You are watching all bug