From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: Copying and pasting Cyrillic text between Emacs and other apps
Date: 29 Jan 2004 08:04:54 +0200 [thread overview]
Message-ID: <uektjl27t.fsf@elta.co.il> (raw)
In-Reply-To: <36b165a.0401281140.4e2b26c@posting.google.com> (paulgor@compuserve.com)
> From: paulgor@compuserve.com (Paul Gorodyansky)
> Newsgroups: gnu.emacs.help
> Date: 28 Jan 2004 11:40:13 -0800
>
> To see Windows code page I use 2 things:
> a) go to Console and type
> chcp
> it returns OEM code page, say 850 and thus I know that
> Windows code page is 1252 :)
> MS has all that listed:
> http://www.microsoft.com/globaldev/reference/cphome.mspx
>
> b) have my own 2-line C program that calls GetACP()
> and puts it on screen :) so I can see
> "System Code Page: 1252"
It turns out my wording was inaccurate and thus misleading. What I
wanted to see was what codepage was used to encode the characters.
You seem to be assuming that this codepage is always identical to the
system codepage, but that is not really true, at least not on Windows
XP. Try copying into the clipboard Cyrillic characters from the
Explorer on a non-Cyrillic Windows machine, and you will see that
CF_TEXT is encoded in cp1251 even though the system codepage is
something different.
> As for characters and their Unicode codepoints:
> a) Start/Run - charmap - and I can see a Unicode # for
> each symbol
> b) http://www.unicode.org/unicode/reports/tr24/charts/index.html
Sure, there are lots of places where Unicode codepoints of the
characters are listed, but what I wanted to know is how does Windows
encode them in the clipboard. It turns out they use the 16-bit
Unicode codepoints, at least for the BMP. (Out of curiosity: do you
or anyone else know how does Windows encode characters outside the
BMP? Is it UTF-16 or something else?)
next prev parent reply other threads:[~2004-01-29 6:04 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
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 [this message]
[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=uektjl27t.fsf@elta.co.il \
--to=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).