On Sat, Feb 24, 2018 at 2:17 PM, Adam Thorn <al...@cam.ac.uk> wrote: > On 24/02/2018 14:16, Nick Couchman wrote: > > Beyond that, the only other possibility I can think of (outside of the >> options you've outlined above) is that we should be UTF-16 encoding it, >> but should using something other than a null terminator for the second >> byte? I have no idea if there's any validity to this idea, or if >> there's anything else you could possibly use besides the null >> terminator, so this option may be totally unreasonable. >> > > I've not looked at any of the RDP-related code or spec, but one thing I've > encountered in other MS specifications is that there are places where they > use UTF-16LE, and are not always as diligent as one might like when it > comes to specifying byte ordering - so another possibility might be to try > e.g. "\0G" rather than "G\0" for a suitably encoded "G". > > Adam > > Good point - probably worth taking a look at that, too.
-Nick
