From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-26 8f18d12: Improve documentation of decoding into a unibyte buffer Date: Tue, 28 May 2019 07:17:35 +0300 Message-ID: <7F0B61E6-C0CA-449B-B432-095569589168@gnu.org> References: <20190525191039.14136.23307@vcs0.savannah.gnu.org> <20190525191040.CCD6C207F5@vcs0.savannah.gnu.org> <83v9xv2649.fsf@gnu.org> <83imtv1fbf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="6856"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: K-9 Mail for Android To: emacs-devel@gnu.org,Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 28 06:18:19 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hVTZ4-0001e9-WD for ged-emacs-devel@m.gmane.org; Tue, 28 May 2019 06:18:19 +0200 Original-Received: from localhost ([127.0.0.1]:56886 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVTZ3-0002or-Mm for ged-emacs-devel@m.gmane.org; Tue, 28 May 2019 00:18:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:42981) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVTYQ-0002om-Mo for emacs-devel@gnu.org; Tue, 28 May 2019 00:17:39 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52566) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hVTYQ-0006l9-Ek; Tue, 28 May 2019 00:17:38 -0400 Original-Received: from [176.12.139.251] (port=53319 helo=[10.163.36.4]) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1hVTYP-0003tZ-TM; Tue, 28 May 2019 00:17:38 -0400 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:237071 Archived-At: On May 28, 2019 5:56:18 AM GMT+03:00, Stefan Monnier wrote: > >> > For a multibyte string that was encoded already, encoding by > >> > utf-8-emacs-unix is IMO the _only_ thing that makes sense=2E > >> I disagree: a multibyte string that was encoded already should only > >> contain ASCII and "eight-bit raw byte chars" > > But both ASCII and raw bytes have multibyte representation=2E >=20 > Not sure why you say "but" here: I was also talking abut a multibyte > string, so I obviously agree=2E >=20 > > If the destination of the encoding is a multibyte buffer, that is > what > > you get there, and then taking buffer-substring will give you > > a multibyte string with encoded text=2E I don't see why we shouldn't > > support this scenario=2E >=20 > I'm not sure where you read that I was arguing we shouldn't support > this scenario=2E I was just pointing out that utf-8-emacs-unix is not > the > only thing that makes sense: string-to-unibyte should work just as > well > (if not better)=2E >=20 >=20 > Stefan string-to-unibyte is also marked obsolete=2E Robert was asking how to use= encoding functions instead of the obsolete string-as-unibyte; advising to = use yet another obsolete function makes little sense to me=2E