diff options
| author | Gerald Combs <gerald@wireshark.org> | 2020-06-24 16:02:39 -0700 |
|---|---|---|
| committer | Gerald Combs <gerald@wireshark.org> | 2020-07-06 16:20:25 +0000 |
| commit | 4dc3114c050ac2fb6da2b19103ce4995f6d91561 (patch) | |
| tree | 08c7406a69bd8bc383f205cd5789556abcf6bdb4 /doc | |
| parent | 0d7d7fe3c6295cd40e3c96407f7208ef19b43b61 (diff) | |
Windows: Set our locale to ".UTF-8".
In each of our executables we were calling "setlocale(LC_ALL, "")" at
startup. This told Windows that output was encoded using the current
system code page. Unless the code page was 65001 (UTF-8), this was a lie.
We write UTF-8 to stdout and stderr, so call "setlocale(LC_ALL, ".UTF-8)"
at startup on Windows. This lets the CRT translate our output correctly
in more cases.
Clarify and expand the OUTPUT section in the tshark man page.
Bug: 16649
Change-Id: If93231fe5b332c292946c7f8e5e813e2f543e799
Reviewed-on: https://code.wireshark.org/review/37560
Petri-Dish: Gerald Combs <gerald@wireshark.org>
Tested-by: Petri Dish Buildbot
Reviewed-by: Gerald Combs <gerald@wireshark.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tshark.pod | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/tshark.pod b/doc/tshark.pod index 4344f625e6..a175c383fd 100644 --- a/doc/tshark.pod +++ b/doc/tshark.pod @@ -1986,8 +1986,11 @@ If B<TShark> detects that it is writing to a TTY on UNIX or Linux and the locale does not support UTF-8, output will be re-encoded to match the current locale. -If B<TShark> detects that it is writing to a TTY on Windows, output will be -encoded as UTF-16LE. +If B<TShark> detects that it is writing to the console on Windows, +dissection output will be encoded as UTF-16LE. Other output will be +UTF-8. If extended characters don't display properly in your terminal +you might try setting your console code page to UTF-8 (B<chcp 65001>) +and using a modern terminal application if possible. =head1 ENVIRONMENT VARIABLES |