On Fri, May 13, 2011 at 05:56:53PM -0400, Brian Hinz wrote:
> Awesome! Thanks for making the class changes, that's been on my TODO list
> since we discussed this last...
You should look at the character encoding handling too:
InStream.readString interprets input data as ISO-8859-1.
CMsgReader.readServerCutText
interprets data as platform encoding (there are even JVMs out there with ASCII
incompatible
plattform encoding). VncAuth limit the supported password characters to
ISO-8859-1 (and will
probably break, if the server uses UTF-8 for password checking).
CMsgWriter.writeClientCutText sends the Clipboard in plattform encoding.
OutStream.writeString sends as ISO-8859-1 (converting any non ISO-8859-1 bytes
to garbage).
CSecurityPlain/Managed send Strings in plattform encoding.
Regards,
Martin K?gler
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
