Wireshark · Wireshark-dev: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)

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] UTF8 vs. locale in error messages (bug 5715)

From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>

Date: Tue, 28 Jun 2011 10:25:07 +0100

On 28/06/2011 01:58, Guy Harris wrote:
>
> 	2) Windows, where "Unicode" generally means "UTF-16", and APIs that return strings encoded as sequences of octets rather than hexadectets probably return strings in the local code page.
>
Is this a first sighting of a new word "hexadectet"? Google doesn't have an
entry for it.

-- 
Regards,

Graham Bloice

Follow-Ups:
- Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
  - From: Guy Harris

References:
- [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
  - From: Stig Bjørlykke
- Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
  - From: Guy Harris

Prev by Date: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
Next by Date: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
Previous by thread: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
Next by thread: Re: [Wireshark-dev] UTF8 vs. locale in error messages (bug 5715)
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube