https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5405
Bill Meier <wmeier@xxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
--- Comment #8 from Bill Meier <wmeier@xxxxxxxxxxx> 2010-12-21 18:54:48 EST ---
Wait , Wait ...
Uh: Are we talking the interface_name or the (vendor) description ?
Ans: (I guess) the description.
My info above was about the "interface name" which is stored in the Windows
registry.
Looking at the winpcap code some more, the vendor description is obtained from
the vendor driver itself (natch). I expect that what Guy said above also
applies to Windows.
"There's no guarantee that the [...] description is in any particular
encoding (other than that the encoding is presumably ASCII-based). At best, we
can probably assume it's in the current locale, although it's probably in the
"system" locale, which might not be the same locale as the user's locale".
So: if we assume that the description is probably encoded in the system locale
and that the user locale is probably the same as the system locale, it sounds
like the description is what really needs to converted using g_locale_to_utf8.
Looking at the Wireshark code, I see that there are some cases where the
description strings are printed and other cases where the description strings
are used in GTK functions. If the description strings returned from
get_interface_list are (converted to) UTF-8 then I think that for any place
they are printed they would need to be converted back to the current locale.
It's starting to get complicated and I think needs more analysis. I won't be
able to pursue this any further until after the holidays, so if anyone else
wants to run with this, feel free.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
