Hi,
+-From: Bubba Meetze <[EMAIL PROTECTED]> --
|_Date: Mon, 3 Mar 2008 04:23:25 -0800 (PST) __
|
|One thing that your proposed addition of the
|setCommand I am guessing is a method that would set
|the command without performing the getBytes call which
|was converting my c
That was one of the things I couldn't figure out for
all of the different encodings how this could be
resolved.
One thing that your proposed addition of the
setCommand I am guessing is a method that would set
the command without performing the getBytes call which
was converting my command to a non
Hi,
+-From: Bubba Meetze <[EMAIL PROTECTED]> --
|_Date: Sun, 2 Mar 2008 17:10:04 -0800 (PST) __
|
|If a user places unicode/utf-8 characters into the
|command the line:
|buf.putString(command.getBytes());
|converts them to non-unicode by doing a
|command.getBytes() call
If a user places unicode/utf-8 characters into the
command the line:
buf.putString(command.getBytes());
converts them to non-unicode by doing a
command.getBytes() call.
I'm having a hard time understanding the reasoning how
I figured this out and how is the best way to explain
it. However I had
