From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: `write-region' writes different bytes than passed to it? Date: Tue, 11 Dec 2018 20:05:57 +0200 Message-ID: <83a7lc0whm.fsf@gnu.org> References: <83d0q8136v.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1544553559 32342 195.159.176.226 (11 Dec 2018 18:39:19 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 11 Dec 2018 18:39:19 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Dec 11 19:39:15 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gWmw6-0008Js-4c for geh-help-gnu-emacs@m.gmane.org; Tue, 11 Dec 2018 19:39:14 +0100 Original-Received: from localhost ([::1]:40769 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gWmyC-0004Xp-KH for geh-help-gnu-emacs@m.gmane.org; Tue, 11 Dec 2018 13:41:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43553) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gWmQB-0000jY-Dk for help-gnu-emacs@gnu.org; Tue, 11 Dec 2018 13:06:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gWmQ6-0008LD-6l for help-gnu-emacs@gnu.org; Tue, 11 Dec 2018 13:06:15 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:41797) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gWmQ6-0008L3-1H for help-gnu-emacs@gnu.org; Tue, 11 Dec 2018 13:06:10 -0500 Original-Received: from [176.228.60.248] (port=2867 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gWmQ3-0006Nt-IO for help-gnu-emacs@gnu.org; Tue, 11 Dec 2018 13:06:08 -0500 In-reply-to: (message from Stefan Monnier on Tue, 11 Dec 2018 11:36:13 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118969 Archived-At: > From: Stefan Monnier > Date: Tue, 11 Dec 2018 11:36:13 -0500 > > > Yes, because "\xC1\xB2" just happens to be the internal multibyte > > representation of a raw-byte F2. Raw bytes are always converted to > > their single-byte values on output, regardless of the encoding you > > request. > > Maybe we shouldn't encode unibyte strings (under the assumption > that a unibyte string is already encoded: it's a sequence of bytes > rather than a sequence of chars). I'm not sure that single use case is important enough to change something that was working like that since Emacs 23. Who knows how many more important use cases this will break? This whole area is crawling with heuristics, whose only justification is that it does TRT in the vast majority of use cases.