Use FT_STRING for string-valued fields.

Have RDP_FI_STRING set for all string-valued fields, with:

	RDP_FI_UNICODE set if the string is always "Unicode" (assumed to
	be UTF-16-encoded);

	RDP_FI_ANSI set if the string is always "ANSI" (we should try to
	use the code page indication);

	neither set if the string is "Unicode" or "ANSI" depending on
	the INFO_UNICODE flag in the packet (the only strings that work
	that way are in TS_INFO_PACKET or TS_EXTENDED_INFO_PACKET
	packets, which also have the flags field with INFO_UNICODE).

Use proto_tree_add_item() to add the string items.

While we're at it, pull the code to get conversation data, creating it
if necessary, into a routine.

svn path=/trunk/; revision=54235

0 files changed, 0 insertions, 0 deletions