From: Jason Rumney <jasonr@gnu.org>
To: "cmr.Pent@gmail.com" <cmr.Pent@gmail.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Face problems when yanking cyrillic text from other X applications
Date: Mon, 05 Nov 2007 21:21:02 +0000 [thread overview]
Message-ID: <472F893E.1080909@gnu.org> (raw)
In-Reply-To: <1194258557.962041.108510@50g2000hsm.googlegroups.com>
cmr.Pent@gmail.com wrote:
> Yes, looks like it is an encoding problem:
>
> character: а (54225, #o151721, #xd3d1, U+0430)
> charset: japanese-jisx0208 (JISX0208.1983/1990 Japanese Kanji: ISO-
> IR-87.)
> code point: #x27 #x51
> syntax: w which means: word
> category: Y:Cyrillic characters of 2-byte character sets j:Japanese
> |:While filling, we can break a line at this character.
> buffer code: #x92 #xA7 #xD1
> file code: #xD0 #xB0 (encoded by coding system mule-utf-8-unix)
> display: by this font (glyph code)
> -JIS-Fixed-Medium-R-Normal--16-150-75-75-C-160-JISX0208.1983-0
> (#x2751)
>
> There are text properties here:
> fontified t
>
Have a look at the variable x-select-request-type. I think setting it to
'UTF8_STRING should give better results. I thought this was the default,
but reading the doc string, it appears that the default is to use some
sort of heuristic. I'm not sure why the heuristic prefers iso-2022-jp
encoded Cyrillic over UTF8 encoding in a ru_RU.UTF-8 locale.
next prev parent reply other threads:[~2007-11-05 21:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 13:45 Face problems when yanking cyrillic text from other X applications Andrey
2007-11-03 15:58 ` Eli Zaretskii
[not found] ` <mailman.2935.1194105535.18990.bug-gnu-emacs@gnu.org>
2007-11-05 10:29 ` cmr.Pent
2007-11-05 20:14 ` Eli Zaretskii
2007-11-05 21:21 ` Jason Rumney [this message]
2007-11-05 22:31 ` Jason Rumney
[not found] ` <mailman.3017.1194297672.18990.bug-gnu-emacs@gnu.org>
2007-11-06 18:53 ` cmr.Pent
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=472F893E.1080909@gnu.org \
--to=jasonr@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=cmr.Pent@gmail.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.