Allow non-ASCII characters in NameService lookups

The underlying problem is that Yoko explicitly disallows characters > 127.
This means that only US-ASCII characters are permitted.
Since the codeset for (narrow) chars and strings can (and should) be negotiated as UTF-8, all characters should be transmissible.
Yoko's character conversion code seems to pre-date porting to Java, and is clearly in need of updating.
