unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Copying and pasting Cyrillic text between Emacs and other apps
Date: Wed, 28 Jan 2004 08:36:39 -0500	[thread overview]
Message-ID: <E1Alprz-0003QR-FV@fencepost.gnu.org> (raw)
In-Reply-To: <uad48wj0r.fsf@jasonrumney.net> (message from Jason Rumney on Wed, 28 Jan 2004 04:00:41)

> > What is it that Emacs doesn't do right here?
> 
> Emacs doesn't use UNICODE_TEXT format. Maybe it should, but we have
> to detect if it is available somehow

The MSDN docs says that the function IsClipboardFormatAvailable can be
used to see if CF_UNICODETEXT is supported.  Can Emacs use that
function?

> since blindly using it will cause other apps to see nothing on the
> clipboard.

It seems like the recommended practice is to put the text into the
clipboard several times in different formats, with the more powerful
formats first.  Windows applications are supposed to walk the list of
available data formats and use the first one they support.

So Emacs could put a CF_UNICODETEXT object, then the CF_TEXT object
into the clipboard, and the Windows apps will then use the Unicode
encoding if they can, else the system page encoded text.

When getting text from the clipboard, Emacs should try CF_UNICODETEXT
first, if it's present in the clipboard (EnumClipboardFormats could be
used to check that).

Of course, this means the effect of "C-x RET x" and "C-x RET X" on
Windows should be rethought...

  reply	other threads:[~2004-01-28 13:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27  4:08 Copying and pasting Cyrillic text between Emacs and other apps eMaXer
2004-01-27 23:16 ` Paul Gorodyansky
2004-01-28  0:25   ` Jason Rumney
2004-01-28  6:33     ` Eli Zaretskii
     [not found]     ` <mailman.1484.1075271523.928.help-gnu-emacs@gnu.org>
2004-01-28  8:54       ` Jason Rumney
2004-01-28 13:36         ` Eli Zaretskii [this message]
2004-01-28 19:31         ` Paul Gorodyansky
2004-01-28 20:31           ` Jason Rumney
2004-01-29  5:29             ` Paul Gorodyansky
2004-01-29  8:54               ` Jason Rumney
     [not found]     ` <mailman.1502.1075297883.928.help-gnu-emacs@gnu.org>
2004-01-28 19:40       ` Paul Gorodyansky
2004-01-29  6:04         ` Eli Zaretskii
     [not found]     ` <mailman.1500.1075297455.928.help-gnu-emacs@gnu.org>
2004-01-28 20:28       ` Jason Rumney
2004-01-29  6:17         ` Eli Zaretskii
2004-01-28  6:27   ` Eli Zaretskii
2004-01-28  7:55     ` Eli Zaretskii
2004-01-28  9:29     ` Eli Zaretskii
     [not found]     ` <mailman.1491.1075282404.928.help-gnu-emacs@gnu.org>
2004-01-28 20:32       ` Paul Gorodyansky
2004-01-29  6:14         ` Eli Zaretskii
     [not found]   ` <mailman.1483.1075271175.928.help-gnu-emacs@gnu.org>
2004-01-28  9:01     ` Jason Rumney
2004-01-28 13:48       ` Eli Zaretskii
2004-01-28 19:45     ` Paul Gorodyansky
2004-01-28 19:57       ` Kevin Rodgers
2004-01-29  5:55       ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Alprz-0003QR-FV@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=eliz@elta.co.il \
    /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: link
Be 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).