Wireshark-dev: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 28 Jun 2011 12:37:42 -0700
On Jun 28, 2011, at 12:25 PM, Stig Bjørlykke wrote:

> On Tue, Jun 28, 2011 at 7:27 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:
>> OK, what OS are you using?
> 
> Snow:~ stig$ uname -a
> Darwin ...

Well, that answers *that* question. :-)

So the locale's encoding should probably be UTF-8, given that it's OS X.

However, if LANG is blank, you presumably don't have Terminal set up to "Set local enviornment variables on startup" (Preferences > Settings > Advanced, at the bottom); I think I turned that on a while ago, perhaps to get some UN*X software to correctly handle UTF-8.  Just out of curiosity, if you set that (or if you explicitly set LANG to something appropriate ending in ".UTF-8", whether it's no_NO.UTF-8, nn_NO.UTF-8, nb_NO.UTF-8, en_NO.UTF-8, or some other setting), does that make the GUI problem go away with a version of Wireshark *without* the

	http://anonsvn.wireshark.org/viewvc?revision=37812&view=revision

changes?

(Whether it has other side-effects is another matter; it might, for example, affect the parsing and output of numbers and dates, for better or for worse.)