Thanks for your comments, Guy and LEGO.
The multiline text field which I planned to add would look a simple
multiline text field, using GtkText, and its internal data structure
would be a list of strings, usgin Glist.
As for the issue of the preferences file, it'd converts a list of
strings into a single-line string and put it into the preferences
file as a line. I thought using a '\n' as a line separator would be ok.
e.g.
The original list contains "text/xml", "application/xml" and "foo\bar"
will be converted to "text/xml\napplication/xml\nfoo\\bar".
I don't think putting some strings in a singleline text field is
user-friendly even though it's effective enough. In XML media types
case, it's kinda hard stuff to read a long string. However, LEGO's
workaround using dummy dtd files is very simple and nice.
So, if no one think the multiline preference field is needed for
ethereal (not only for the XML dissector), I'll use LEGO's
workaround just for myself and will look forward to someone doing
tvbparser work as LEGO explained :-)
Thanks,
- endoh
