unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: romain@orebokech.com, jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: Cut buffers and character encoding
Date: Sun, 12 Nov 2006 00:14:33 -0500	[thread overview]
Message-ID: <E1Gj7ft-0000j7-Gf@fencepost.gnu.org> (raw)
In-Reply-To: <E1Gis9w-0002If-00@etlken> (message from Kenichi Handa on Sat, 11 Nov 2006 21:40:32 +0900)

    I think tring locale-coding-system at first, and if that
    yields undecoded eight-bit characters, decoding by
    iso-8859-1 is good.

That is not a good idea.  locale-coding-system is set based on the
locale, and people set their locales for general reasons, not
specifically about Emacs.  It would be undesirable to choose
nonstandard behavior for cut buffers merely because someone normally
uses latin-2, for instance.

It is ok to have a feature to specify nonstandard encoding of
cut-buffers, but it should be a specific feature, which affects
nothing else, and which people will enable only when they specifically
want nonstandard encoding of cut-buffers.

  reply	other threads:[~2006-11-12  5:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09  7:39 Cut buffers and character encoding Romain Francoise
2006-11-09 19:10 ` Jan D.
2006-11-09 20:56   ` Romain Francoise
2006-11-10  7:42     ` Jan D.
2006-11-10 10:24       ` Kenichi Handa
2006-11-10 13:39         ` Romain Francoise
2006-11-11 12:40           ` Kenichi Handa
2006-11-12  5:14             ` Richard Stallman [this message]
2006-11-18  2:23               ` Kenichi Handa
2006-11-18 13:18                 ` Jan Djärv
2006-11-20  3:23                   ` Katsumi Yamaoka
2006-11-20  7:44                     ` Jan Djärv
2006-11-20  7:57                       ` Katsumi Yamaoka
2006-11-20 23:58                       ` Richard Stallman
2006-11-21 12:47                         ` Jan Djärv
2006-11-18 16:05                 ` Richard Stallman
2006-11-10 18:41   ` Richard Stallman

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=E1Gj7ft-0000j7-Gf@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=romain@orebokech.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).