To Grishka: Um, I think you meant "CopyUnicode" rather than "ClipUnicode".
No, his instructions are correct as given. It does mean that the JAR file produced will have a different name. Jon takes a different approach, which preserves the CopyUnicode name for the JAR. See Grishka's response below. --AC
IMPORTANT: Make sure the checkbox is checked when copying to Mudcat. If you don't, you'll see the raw character in the message entry area instead of a sequence beginning with ampersand. This means you're doing it wrong!
For instance, above, where Jon pasted the odd-looking "Hello", the characters were inserted raw. The input system did properly encode the first four characters automatically, but the o-umlaut was not encoded. Switch your view encoding for this page to, say, MacRoman (a common default for Mac users), and instead you'll see a lone circumflex accent. If you're encoding things properly, you should see all the text correctly no matter which view encoding is in effect.