help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Copying and pasting Cyrillic text between Emacs and other apps


From: Paul Gorodyansky
Subject: Re: Copying and pasting Cyrillic text between Emacs and other apps
Date: 28 Jan 2004 11:40:13 -0800

Eli Zaretskii <eliz@gnu.org> wrote in message 
news:<mailman.1502.1075297883.928.help-gnu-emacs@gnu.org>...
> 
> I wanted something that will show me the Windows codepage and the
> Unicode codepoints of the characters;

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"

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

> 
> I found ClipConvert and (its newer incarnation) Album that do what I
> wanted.  They can also convert between encodings and CF_* formats, so
> it looks like there's another alternative for Paul Gorodyansky's page.

Thanks! I'll look at it.


-- 
Regards,
Paul Gorodyansky
"Cyrillic (Russian): instructions for Windows and Internet": 
http://ourworld.compuserve.com/homepages/PaulGor/

> 
> > The locale can't be viewed, but it seems that Emacs might be able to
> > do something with that to get text that Emacs puts on the clipboard
> > in the right encoding.
> 
> Yes.
> 
> > But it cannot influence how other apps put text on the clipboard
> > (which AFAIK is always in the System locale, even if the characters
> > cannot be encoded in that).
> 
> It seems like on Windows XP, the characters are implicitly converted
> to Unicode (by some internal Windows machinery), so Emacs can always
> win using CF_UNICODETEXT if it's available in the clipboard.  Failing
> that, we can again use CF_LOCALE to determine the correct encoding
> with which to decode CF_TEXT text.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]