From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Encoding of etc/HELLO Date: Mon, 23 Apr 2018 19:25:41 +0300 Message-ID: <83fu3lx52y.fsf@gnu.org> References: <83sh7qxb5j.fsf@gnu.org> <87po2t6gdm.fsf@gmx.de> <87in8l6ap1.fsf@gmx.de> <8736zopahx.fsf@mail.linkov.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1524500703 8973 195.159.176.226 (23 Apr 2018 16:25:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 23 Apr 2018 16:25:03 +0000 (UTC) Cc: eggert@cs.ucla.edu, michael.albinus@gmx.de, emacs-devel@gnu.org To: Juri Linkov , Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 23 18:24:59 2018 Return-path: Envelope-to: ged-emacs-devel@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 1fAeGx-0002Bf-7G for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2018 18:24:59 +0200 Original-Received: from localhost ([::1]:54365 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAeJ4-0007a3-3O for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2018 12:27:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAeHs-0007Xr-Ns for emacs-devel@gnu.org; Mon, 23 Apr 2018 12:25:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fAeHr-0000zs-Rx for emacs-devel@gnu.org; Mon, 23 Apr 2018 12:25:56 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44544) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fAeHo-0000y2-2T; Mon, 23 Apr 2018 12:25:52 -0400 Original-Received: from [176.228.60.248] (port=3856 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fAeHn-0003fi-Hb; Mon, 23 Apr 2018 12:25:51 -0400 In-reply-to: <8736zopahx.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 21 Apr 2018 23:31:22 +0300) 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: 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:224815 Archived-At: > From: Juri Linkov > Cc: Paul Eggert , Eli Zaretskii , emacs-devel@gnu.org > Date: Sat, 21 Apr 2018 23:31:22 +0300 > > I don't understand why it's impossible to create a charset like the > existing mule-unicode-e000-ffff but for character range over U+FFFF > to include such characters as U+1F44B. Or is this an inherent limitation > of the iso-2022-7bit coding system? I'm not sure I understand your proposal. Are you suggesting to create a Mule charset covering just the Emoji block? That could be possible (assuming ISO-2022 still has vacant charset slots available, something that I don't think I know how to determine reliably, and assuming we decipher the black art of using define-charset). But is this worth doing it just for Emoji? If you mean to add a larger range of characters, then I think a single ISO-2022 compatible charset can support at most 8192 character, so we will need a lot of charsets to cover codepoints between U+10000 and U+2FFFF, and I'm not sure we have that many vacant slots. Or did you mean to suggest something else?