Re: USTRING "encoding" behavior different from STRING's?

>
> I was using the "encoding" kwarg for STRING to automatically encode my
> string
> to utf16_be, however, it seems when the packet is never written with the
> encoding when using USTRING.  STRING has been deprecated in favor of
> USTRING,
> is the behavior of encoding supposed to change?


The encoding keyword was only temporary in the STRING class, we decided not
to include it in favor of introducing USTRING and deprecating STRING to
reduce impact on existing code.
You should not use STRING any more.

It sounds like you are having a problem with the USTRING class. Do you have
the latest updates? Can you provide an example of the packet you defined?

Simon