Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 12763] tshark print 'TCP flags' with non-ascci chars on some console

[bugzilla-daemon@xxxxxxxxxxxxx]

Comment # 4 on bug 12763 from Gerald Combs

What do the commands `locale` and `env | grep -i utf` show? Also, do either of

LESSCHARSET=utf-8 ./tshark ... | less

or

./tshark -E bom=y ... | less

make the mojibake go away?

The TShark man page in master and master-2.2 says,

    TShark uses UTF-8 to represent strings internally. In some cases the
    output might not be valid. For example, a dissector might generate invalid
    UTF-8 character sequences. Programs reading TShark output should expect
    UTF-8 and be prepared for invalid output.

    If 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 TShark detects that it is writing to a TTY on Windows, output will be
    encoded as UTF-16LE.

Even though your locale is "C", TShark is generating UTF-8 because you're
piping to less instead of writing to a TTY.

---

      You are receiving this mail because:

• You are watching all bug changes.