From: jsbien@mimuw.edu.pl (Janusz S. Bień)
Subject: Re: X-Windows cut&paste problems (Japanese characters)
Date: 28 Sep 2003 19:12:22 +0200 [thread overview]
Message-ID: <87wubson0p.fsf@mimuw.edu.pl> (raw)
In-Reply-To: 7137-Sat27Sep2003134932+0300-eliz@elta.co.il
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2177 bytes --]
On Sat, 27 Sep 2003 "Eli Zaretskii" <eliz@elta.co.il> wrote:
> > From: jsbien@mimuw.edu.pl (=?iso-8859-2?q?Janusz_S._Bie=F1?=)
> > Date: 25 Sep 2003 18:00:10 +0200
> >
> > I have recently observed several problems concerning cut&paste between
> > Emacs and some applications (Debian unstable, IceWM and GNOME).
>
> The version of your Emacs will be of help, of course ;-)
I've just tested that the problem occurs also in CVS Emacs, so I
cross-post to emacs-devel.
When I paste two kanji characters from Mozilla (Debian package 1.4-4)
to Emacs 21.3.1. from the Debian package or to the CVS version
compiled by myself (21.3.50.1), I get
\x{65E5}\x{672C}
The numbers in braces are the correct Unicode code points of the
characters in question.
I repeated the experiment in a different Debian installation. When I
paste from Galeon 1.2.5 to Emacs 21.2.1 from the Debian package, I get
just 2 question marks. However, when I paste them into exactly the
same CVS version as above, I get two strange characters (displayed as
question signs in reverse video), the first one being reported as "c
with acute":
------------------------------------------------------------------------
character: Ä (0346, 230, 0xe6, U+65E5)
charset: eight-bit-graphic (8-bit graphic char (0xA0..0xFF))
code point: 230
syntax: which means: whitespace
buffer code: 0xE6
file code: not encodable by coding system iso-8859-2
font: -ETL-Fixed-Medium-R-Normal--16-160-72-72-C-80-ISO8859-1
Composed with the following character(s) `Â¥' to form `æ¥'.
There are text properties here:
fontified t
untranslated-utf-8 26085
composition (0 3
[326333])
-----------------------------------------------------------------------
The Unicode code point is correct, but the rest seems a complete mess
:-(.
Las but not least, a good news: the characters are pasted correctly in
unicode-emacs.
Best regards
Janusz
--
,
dr hab. Janusz S. Bien, prof. UW
Prof. Janusz S. Bien, Warsaw Uniwersity
jsbien@mimuw.edu.pl, jsbien@uw.edu.pl
http://www.mimuw.edu.pl/~jsbien/
next prev parent reply other threads:[~2003-09-28 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 17:09 Meta key, Alt key & ESC Bertram Scharpf
2003-01-05 19:26 ` Kai Großjohann
2003-01-05 21:42 ` Bijan Soleymani
2003-09-25 16:00 ` X-Windows cut&paste problems (Japanese characters) Janusz S. Bień
2003-09-27 11:49 ` Eli Zaretskii
2003-09-28 17:12 ` Janusz S. Bień [this message]
2003-09-28 17:43 ` Miles Bader
2003-09-29 15:14 ` Janusz S. Bień
2003-09-29 16:09 ` Jason Rumney
2003-01-06 2:11 ` Meta key, Alt key & ESC Tim X
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=87wubson0p.fsf@mimuw.edu.pl \
--to=jsbien@mimuw.edu.pl \
/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).