From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Bugfix for utf-8 XTerm/MinTTY and (set-input-meta-mode t) Date: Tue, 01 Jun 2021 16:06:48 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16512"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: "emacs-devel@gnu.org" To: Max Mikhanosha Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 01 22:08:49 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1loAgz-00047X-Ae for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Jun 2021 22:08:49 +0200 Original-Received: from localhost ([::1]:33878 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1loAgx-0001HC-UV for ged-emacs-devel@m.gmane-mx.org; Tue, 01 Jun 2021 16:08:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39372) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loAf9-0007Ys-Iy for emacs-devel@gnu.org; Tue, 01 Jun 2021 16:06:55 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:35496) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1loAf7-0005MN-9F for emacs-devel@gnu.org; Tue, 01 Jun 2021 16:06:54 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4AB2E1002E9; Tue, 1 Jun 2021 16:06:51 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id BFBC3100201; Tue, 1 Jun 2021 16:06:49 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1622578009; bh=/GEVKXHkSZovDIBkS/vumfaDq0mpyTlqk4P9EWhGaNE=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=bQEeHMk+hMsEGgN1A1oD1h03/g0rweg7wniyOMS4sWJhwYNmL5aD1jehNjEtAl2Wz WZZYXaiGrLAwiFtuVjz8qLmKOcamlxunaqsZODDKOmSNkpF15dwavfRPQHituLWzol p57Inb+aiT4/gUckhUemTVffMs66XElROqCFFV/Y+nmz9TgdQlZlRWZmEDzmUzh58+ 3qNfL1aevip8J3+VEUsPM0KhuUM+kNHyRLDyndIi6c0wJglUGME9HqjsoLVaP8rowA FxnL6/bUinpbpVxRWC6+W8ePLmK2vEchYrm/lYtpgAm4ilPkdZKCSkcFc7RUUYC0jB Je/AcCtQlrpQA== Original-Received: from alfajor (69-196-163-239.dsl.teksavvy.com [69.196.163.239]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 95093120210; Tue, 1 Jun 2021 16:06:49 -0400 (EDT) In-Reply-To: (Max Mikhanosha's message of "Tue, 01 Jun 2021 16:19:40 +0000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:270248 Archived-At: > Both XTerm and MinTTY, when configured to send meta modifier as 8th > bit while in utf-8 mode, will first add 8th bit, and then encode > resulting character with utf-8. For example Meta-X is encoded > as ?x+128 =3D #248 codepoint, encoded as 0xc3,0xb8 How did they end up with that weird design? I mean they could have made meta toggle the 24th bit, for example, so it doesn't collide with other existing characters. This design is quite weird since it breaks all the latin-1 chars of unicode plus all the uses of meta with non-ASCII chars. How do they encode M-=CE=BB ? Is it also sent as the same byte-sequence as `?=CE=BB + 128 =3D ?=D0=BB` ? Admittedly, it is better than the "original" meta-as-8th-bit which was limited to ASCII, but it still seems unnecessarily limited and kludgey. Stefan