Wireshark-dev: Re: [Wireshark-dev] Making a dissector for a text proto using ISO 10646 (Unicode
About XML/DTD:
The XML dissector would need far more than FT_STRING_UNICODE to handle
XML with multibyte encoded chars .
The tvbparse API (on which the xml dissector) would need to be exteded
to handle multi-byte chars. And some parts of how to do it aren't
clear to me. What about multibyte chars in entities data and/or
entity/element/attribute names in DTDs? That means that the DTD
parser needs to be extended as well.
\Lego
PS: In theory for adding support for an XML protocol all you need is
to write a DTD.
On Fri, Oct 3, 2008 at 11:59 AM, Anders Broman
<anders.broman@xxxxxxxxxxxx> wrote:
> 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 ?
> ________________________________
> From: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of
> scott.harman@xxxxxxxxxxx
> Sent: den 1 oktober 2008 14:30
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] Using external DTD
>
>
> 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
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> https://wireshark.org/mailman/listinfo/wireshark-dev
>
>
--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan
