Re: [Wireshark-commits] rev 53826: /trunk/epan/ /trunk/epan/: charsets.c charsets.h proto.h tvbuff.c

[Guy Harris <guy () alum mit edu>]

On Dec 7, 2013, at 7:02 AM, darkjames () wireshark org wrote:

> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=53826
>
> User: darkjames
> Date: 2013/12/07 03:02 PM
>
> Log:
> Add string encoding for ISO/IEC 8859-2 (ENC_ISO_8859_2)

Should code points in the range 0x80-0x9F map to 0x80-0x9F?

        https://en.wikipedia.org/wiki/ISO_8859#Introduction

claims (without citing a reference inline) that

        The ISO/IEC 8859-n encodings only contain printable characters, and were designed to be used in conjunction 
with control characters mapped to the unassigned bytes. To this end a series of encodings registered with the IANA add 
the C0 control set (control characters mapped to bytes 0 to 31) from ISO 646 and the C1 control set (control characters 
mapped to bytes 128 to 159) from ISO 6429, resulting in full 8-bit character maps with most, if not all, bytes 
assigned. These sets have ISO-8859-n as their preferred MIME name or, in cases where a preferred MIME name isn't 
specified, their canonical name. Many people use the terms ISO/IEC 8859-n and ISO-8859-ninterchangeably. ISO/IEC 
8859-11 did not get such a charset assigned, presumably because it was almost identical to TIS 620.

and the Unicode code points 0x0080-0x009F are used for the C1-control-set.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe