Re: Face problems when yanking cyrillic text from other X applications

[Jason Rumney]

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.