Re: "Outer world" encoding for non-Latin1 language environments

[Kenichi Handa]

Eli Zaretskii <address@hidden> writes:
> On Wed, 27 Feb 2002, Anton Zinoviev wrote:

>>  Even when users choose some non-Latin1 language environment Emacs
>>  doesn't suppose that it's new default encoding is actually the
>>  encoding of the X-clipboard, the console font, etc.  This can be
>>  easily changed in this way:

> Why change it?  The default for X selections is compound-text, which can 
> handle many different languages/scripts mixed in a single selection.  
> What you propose (to set it to koi8-u) will limit the selections to a 
> single charset.  Why is that a good idea?

It may be good for such koi8-u environment that uses koi8-u
encoding directly for X selection and all the other X
applications expect that.

But, such a usage is against X's ICCCM (Inter-Client
Communication Conventions Manual) that says STRING type
selection can contain ASCII and Latin-1 only.

And it seems that the world is moving toward using UTF-8 or
using "Non-Standard Character Set Encodings" of
compound-text.

Are there any consensus in koi8-u community for such a usage
(i.e. using koi8-u directly in X selection)?

If not, I too agree with Eli.  Keep on using compound-text
as the default coding system for X selection is better.

By the way, the support for "Non-Standard Character Set
Encodings" in compound-text is recently added to Emacs by
the effort of Eli.  Currently it doesn't support koi8-u
because we haven't heard that people started to use that
method for koi8-u.

---
Ken'ichi HANDA
address@hidden