Wireshark-dev: Re: [Wireshark-dev] Making a dissector for a text proto using ISO 10646 (Unicode
Hi,
I took
a quick look at this trace and I think it raises some
questions:
Should
ve make routines to handle Unicode? e.g
tvb_find_line_end_unicode() how should strings be added
to the tree? new FT ( FT_STRING_UNICODE) or ?
Thoughts?
Regards
Anders
> Hi,
> You need to write a
mos dissector ;) The TCP dissector will not interpret the
data.
>
> The data looks
fishy, every ASCII character separated by 00?
Ah:
Encoding
The supported character encoding is ISO 10646
(Unicode) in UCS-2, as defined in The Unicode Standard, version 2.0. All MOS
message contents are transmitted in Unicode, high-order byte first, also known
as “big endian.”
> Regards
> Anders
Hi guys I'm trying to use an externally generated DTD to parse
some traffic I've attached a packet
and my dtd - can anyone point me in the right direction? It's displaying as TCP/XML in Wireshark (1.0.99 and 1.02)
but it's simply not decoding. Can anyone
help me get this working? Many
thanks
Scott
--
This e-mail is intended for the named
addressees only. Its contents may be privileged or confidential and should be
treated as such. If you are not an intended recipient please notify the sender
immediately and then delete it; do not copy, distribute, or take any
action based on this e-mail. In the pursuit of its legitimate business
activities and its conformance with relevant legislation, Quantel may access any
e-mail (including attachments) it originates or receives, for potential
scrutiny.
Quantel is the trade name used by Quantel Holdings Limited and
its subsidiaries. Quantel Holdings Limited is registered in England &
Wales. Registration No: 4004913
Contact details for all Quantel
Offices and Companies can be found on our website www.quantel.com or by writing
to the holding company.
Registered address: Turnpike Road, Newbury,
Berkshire, RG14 2NX, United Kingdom
