Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Missing character in Qt GUI

From: João Valverde <joao.valverde@xxxxxxxxxxxxxxxxxx>
Date: Wed, 14 Oct 2015 21:29:21 +0100


On 10/14/2015 09:15 PM, Guy Harris wrote:

On Oct 14, 2015, at 12:23 PM, Joerg Mayer <jmayer@xxxxxxxxx
<mailto:jmayer@xxxxxxxxx>> wrote:

I currently have a missing character between source and destination
port in the
info column of udp and tcp. See attached screenshot.

I suspect your font doesn't support that glyph. In addition to what Guy said it is in a different unicode block than RIGHTWARDS ARROW, something I was not aware of until now.

I'll submit a change to revert it to RIGHTWARDS ARROW.

That's the Unicode LONG RIGHTWARDS ARROW character.

In TShark, it shows up as

   1   0.000000 10.56.10.106 -> 10.56.10.222 UDP 40392⟶53 Len=43
   2   0.000784 10.56.10.222 -> 10.56.10.106 UDP 53⟶40392 Len=254
   3   5.140107 10.56.10.106 -> 10.56.10.222 UDP 40396⟶53 Len=33
   4   5.141221 10.56.10.222 -> 10.56.10.106 UDP 53⟶40396 Len=201

if you copy and paste from Terminal into this message, so it's there,
but it displays oddly in Terminal on OS X 10.10:


with the LONG RIGHTWARDS ARROW overlapping with the character after it.

If I replace it with the non-long RIGHTWARDS ARROW character, it works.

I've no idea why Qt isn't handling LONG RIGHTWARDS ARROW, but perhaps we
should use a NOT SO LONG RIGHTWARDS ARROW here; it has the disadvantage
that it's a bit small and the advantage that it's the same width as
other characters in the OS X fixed-width font I'm seeing and thus might
not upset Qt or whatever is happening.


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
              mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe