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: Fri, 20 Apr 2018 19:00:30 +0300 Message-ID: <83muxxyijl.fsf@gnu.org> References: <83sh7qxb5j.fsf@gnu.org> <87po2t6gdm.fsf@gmx.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1524240101 6533 195.159.176.226 (20 Apr 2018 16:01:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Apr 2018 16:01:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Apr 20 18:01:37 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 1f9YTh-0001Yj-8O for ged-emacs-devel@m.gmane.org; Fri, 20 Apr 2018 18:01:37 +0200 Original-Received: from localhost ([::1]:39776 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9YVl-0008UO-S7 for ged-emacs-devel@m.gmane.org; Fri, 20 Apr 2018 12:03:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57317) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9YSn-0006AL-BP for emacs-devel@gnu.org; Fri, 20 Apr 2018 12:00:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f9YSm-0006Rp-LK for emacs-devel@gnu.org; Fri, 20 Apr 2018 12:00:41 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42795) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f9YSm-0006RV-IL; Fri, 20 Apr 2018 12:00:40 -0400 Original-Received: from [176.228.60.248] (port=3483 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1f9YSl-0003oH-Un; Fri, 20 Apr 2018 12:00:40 -0400 In-reply-to: <87po2t6gdm.fsf@gmx.de> (message from Michael Albinus on Fri, 20 Apr 2018 17:34:45 +0200) 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:224742 Archived-At: > From: Michael Albinus > Cc: emacs-devel@gnu.org > Date: Fri, 20 Apr 2018 17:34:45 +0200 > > --8<---------------cut here---------------start------------->8--- > When a file is in some legacy encoding such as iso-2022-7bit, Emacs > attached charset properties to proper ranges of text, which works as a > hint for selecting a proper font especially for CJK characters. > --8<---------------cut here---------------end--------------->8--- > > I'm wondering why it is possible to attach charset properties for > iso-2022-7bit, but not for utf-8. Note, that I don't know too much about > this topic. Because we don't have infrastructure for tagging sub-ranges of Unicode with character sets (and in some sense, that would make little sense, because Unicode is a unifying encoding). ISO-2022 has built-in features to tag portions of text as belonging to some specific charset.