https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Evan Huus changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #13 from greenwan...@gmail.com ---
(In reply to comment #12)
> Created attachment 12801 [details]
> windows gtk version, accents fixed
Hi,
I don't know how to start the QT version of wireshark, but for the GTK windows
build v
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #12 from greenwan...@gmail.com ---
Created attachment 12801
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=12801&action=edit
windows gtk version, accents fixed
--
You are receiving this mail because:
You are the as
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Evan Huus changed:
What|Removed |Added
CC||eapa...@gmail.com
--- Comment #11 from
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Evan Huus changed:
What|Removed |Added
CC||greenwan...@gmail.com
--- Comment #10
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #9 from Stephen Fisher 2011-02-11
16:37:04 MST ---
See also bug #5683 "bad display of the network interface in the startup window"
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
--- You
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Bill Meier changed:
What|Removed |Added
Status|ASSIGNED|NEW
--- Comment #8 from Bill Meier 2
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #7 from Guy Harris 2010-12-21 11:49:58 PST ---
> I would say yes, convert it to UTF-8 right away. UTF-8 can represent any
> unicode character, but it may take more bytes than a native UTF-16 or UTF-32
> would.
Although, as m
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #6 from Stephen Fisher 2010-12-21
12:22:27 MST ---
(In reply to comment #4)
> A. I believe that in capture-wpcap.c the pcap_lookupdev() and related code to
> do the unicode to ascii stuff is obsolete and is no longer ever used.
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #5 from Bill Meier 2010-12-21 13:19:28 EST ---
Oops;
In B. above the initial paragraph should have read:
B. I also believe that the actual issue is as follows:
It appears that on Windows pcap_findalldevs returns strings enc
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Bill Meier changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from Bill Mei
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #3 from Stephen Fisher 2010-12-20
15:15:38 MST ---
The culprit is likely in the get_interface_list() function within
capture-wpcap.c. As the comments in that function state, the returned
information from WinPcap are double-byt
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #2 from Stephen Fisher 2010-12-20
14:41:26 MST ---
I attempted to reproduce this by giving my interface the same name as yours,
but in Wireshark instead of Windows providing the name. It shows up properly
on the welcome page (
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
--- Comment #1 from Jaap Keuter 2010-11-15 15:35:10 CET
---
That's not HTML code, but Pango markup
(http://www.gtk.org/api/2.6/pango/PangoMarkupFormat.html). This string should
be converted into valid UTF-8 and rinsed through g_markup_esca
14 matches
Mail list logo
