Control: tags 693293 confirmed upstream On Thu, 15 Nov 2012 08:20:39 +0100 Bernard Jungen <[email protected]> wrote: > When specifying text with -text or -file, it is converted before > being sent, mangling non-ASCII characters and replacing a few other > ASCII characters (I'm using the Belgian layout here), which makes the > utility completely useless with non-ASCII text *or* a non-US keyboard > layout. It should obviously pass the text without any conversion > instead, since the provided text *is* already the text you want the > application to receive. Some extremely minor testing shows that at least ISO-8859-1 input files work as expected in an UTF-8 terminal (using xvkbd default settings). I'll try to figure out if that is really what upstream is doing. I don't think it should always pass the provided text as-is, but instead often it should pass it on in the locale of the receiving client. I can empathize with the request for this being optional.
Upstream has the -utf16 option. If one converts the input file first to UTF-16 and then use the outcome with that option, it seems to work as I expect. Paul
signature.asc
Description: OpenPGP digital signature
