public inbox for cygwin-xfree-announce@sourceware.org help / color / mirror / Atom feed
From: "Harold Hunt" <huntharo@msu.edu> To: "cygx" <cygwin-xfree@cygwin.com>, "cygxannounce" <cygwin-xfree-announce@cygwin.com> Subject: [ANNOUNCEMENT] xwinclip Test 06 (Cygwin/XFree86 and Windows clipboard integration) Date: Fri, 21 Jun 2002 22:35:00 -0000 [thread overview] Message-ID: <NHEELHJHHFKPMAEAFMFCAEBMDAAA.huntharo@msu.edu> (raw) Links: I just posted Test 06 to the xwinclip development page: http://xfree86.cygwin.com/devel/xwinclip/ xwinclip binary and source code releases are available via the sources.redhat.com ftp mirror network (http://cygwin.com/mirrors.html) in the pub/cygwin/xfree/devel/xwinclip/ directory. You may wish to note the desired filename in the links below, then download from your closest mirror (http://cygwin.com/mirrors.html). xwinclip binary, direct link: http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-Test06.exe.bz2 (6 KB) Server source, direct link: http://www.msu.edu/~huntharo/xwin/xwinclip/xwinclip-20020622-0007.tar.bz2 (10 KB) Changes: 1) xevents.c, xevents.h, xwinclip.c - Add real support for COMPOUND_TEXT, TARGETS, and UTF8_STRING selection types. Grab clipboard contents in Unicode, if supported, convert to multi-byte character set, then stick the result into the appropriate target. This allows Japanese text to be transferred via xwinclip. Other eastern languages (Korean, Chinese, etc.) may also work. (Matsuzaki Kensuke) 2) xwinclip.c - Add a UnicodeSupport function to check if we have Unicode support or not. Currently this is done by just checking if we are on an NT-based platform or not. (Harold Hunt) Enjoy, Harold
reply other threads:[~2002-06-22 5:35 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=NHEELHJHHFKPMAEAFMFCAEBMDAAA.huntharo@msu.edu \ --to=huntharo@msu.edu \ --cc=cygwin-xfree-announce@cygwin.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).