On 2020-01-18 04:55, Tobias Boege wrote:
BUT the terminating NUL character is not inserted by NativeCall and it
isn't inserted by &encode.


Hi Tobias,

I found this out the hard way.  I also found out the
hard wasy the UTF16 strings need to be terminated with
a double nul (0x0000).

-T

Reply via email to