The default behavior is not affected if the new command-line parameters are not passed, right? Is there anyway that you can figure out the -winencoding parameter from Windows? I realize that this is an initial version, but it would be wise not to introduce a new command-line parameter only to get rid of it shortly.
Is it a good idea to add a dependency on libiconv? I can't think of any reason why this would be a problem.
Harold
Kensuke Matsuzaki wrote:
Hello,
This patch make xwinclip convert clipboard text encoding using libiconv, so perhaps you can copy and paste non-ASCII characters on Win9x.
But I don't have Win9X, I haven't tested it yet.
I could copy and paste Unicode text on NT/2000/XP, but CJK characters sometimes become other CJK characters because of Han Unification. This patch fix this problem.
For example, I use following command line option on Windows XP. LANG=ja_JP.eucJP XWin -clipboard -nounicodeclipboard -winencoding SHIFT_JIS -xencoding EUC-JP
Test on other language environment and 9x platform needed.
Kensuke Matsuzaki
