osmith
/
wireshark
forked from osmocom/wireshark
1
0
Fork 0
Code Pull Requests Releases Wiki Activity

Mention ENC_UCS_2 and ENC_UTF_16. 

svn path=/trunk/; revision=42602
This commit is contained in:
Guy Harris 2012-05-12 20:10:18 +00:00
parent 3896fea6c0
commit 1c7269a6d1
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/README.developer
View File

@ -2377,15 +2377,21 @@ order.
For string fields, the encoding specifies the character set used for the
string and the way individual code points in that character set are
encoded. For FT_UINT_STRING fields, the byte order of the count must be
specified; when support for UTF-16 encoding is added, the byte order of
the encoding will also have to be specified. In other cases, ENC_NA
should be used. The character encodings that are currently
supported are:
specified; for UCS-2 and UTF-16, the byte order of the encoding must be
specified (for counted UCS-2 and UTF-16 strings, the byte order of the
count and the 16-bit values in the string must be the same). In other
cases, ENC_NA should be used. The character encodings that are
currently supported are:
ENC_UTF_8 - UTF-8
ENC_ASCII - ASCII (currently treated as UTF-8; in the future,
all bytes with the 8th bit set will be treated as
errors)
ENC_UTF_8 - UTF-8
ENC_UCS_2 - UCS-2
ENC_UTF_16 - UTF-16 (currently treated as UCS-2; in the future,
surrogate pairs will be handled, and non-valid 16-bit
code points and surrogate pairs will be treated as
errors)
ENC_EBCDIC - EBCDIC
Other encodings will be added in the future.