On Wed, 10 Nov 2010 10:59:48 +0100, didier <dgautheron@xxxxxxxx> wrote:
> Hi,
> Le mercredi 10 novembre 2010 à 10:01 +0100, Anders Broman a écrit :
>>
>> -----Original Message-----
>> From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Thomas Boehne
>> Sent: den 10 november 2010 09:54
>> To: Developer support list for Wireshark
>> Subject: Re: [Wireshark-dev] non-ASCII stuff in manuf
>>
>> On 10/26/2010 11:32 AM, Thomas Boehne wrote:
>> >> I contacted them a couple of times concerning this, but the requests
>> >> would either not be answered at all or were forwarded to people that
>> >> could not fix the problem. I will try it again today, or probably call
>> >> them until I finally reach somebody that can help.
>> >
>> >After sending a bunch of emails to IEEE explaining the problem in detail, they finally changed the database
>> >entries today.
>> >
>> >The bad news is that they are now _both_ displayed incorrectly on the web page (if the browser decides to
>> >display the page as unicode).
>> >
>> >The good new is that they are both displayed _correctly_ in wireshark, since make-manuf decodes the database as >iso-8859-1.
>> >
>> >Could someone please run make-manuf to update manuf and check it in?
>> >
>> >Best regards
>> >Thomas Böhne
>>
>> It will be automatically run on Sunday...
> On the other hand after all this hard work it'd be nice to fix
> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4102
>
> g_strlcpy doesn't work with UTF8 and these
> 'Pango-WARNING **: Invalid UTF-8 string passed to pango...'
> are a pain.
>
> Didier
>
So this does require g_utf8_strncpy() (and g_utf8_validate() before
that) i.s.o g_strlcpy() ?
Thanks,
Jaap
