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: etc/HELLO markup etc. Date: Sat, 29 Dec 2018 09:37:33 +0200 Message-ID: <83lg486awy.fsf@gnu.org> References: <87wons6bkj.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1546069258 26634 195.159.176.226 (29 Dec 2018 07:40:58 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 29 Dec 2018 07:40:58 +0000 (UTC) Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, Emacs-devel@gnu.org To: handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 29 08:40:54 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 1gd9Er-0006r0-Nl for ged-emacs-devel@m.gmane.org; Sat, 29 Dec 2018 08:40:53 +0100 Original-Received: from localhost ([127.0.0.1]:35162 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gd9Gy-0003zy-9C for ged-emacs-devel@m.gmane.org; Sat, 29 Dec 2018 02:43:04 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:53333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gd9Gj-0003v6-5N for Emacs-devel@gnu.org; Sat, 29 Dec 2018 02:42:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gd9C1-0007yL-DN for Emacs-devel@gnu.org; Sat, 29 Dec 2018 02:37:58 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40639) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gd9Bw-0007tb-LX; Sat, 29 Dec 2018 02:37:52 -0500 Original-Received: from [176.228.60.248] (port=4604 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gd9Bw-0007Xu-8o; Sat, 29 Dec 2018 02:37:52 -0500 In-reply-to: <87wons6bkj.fsf@gnu.org> (message from handa on Sat, 29 Dec 2018 16:23:24 +0900) 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:232030 Archived-At: > From: handa > Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, Emacs-devel@gnu.org > Date: Sat, 29 Dec 2018 16:23:24 +0900 > > > I'm not yet sure this is only about Han unification. Using charsets > > for specifying fonts is a general feature in Emacs, which can be used > > to control which fonts are selected independently of what the OS > > facilities such as fontconfig do. > > > I hope Handa-san will be able to comment on this stuff. > > > If Han unification is the only important user of the charset property, > > then yes, we could remove the rest of the charset info from HELLO. > > Long ago, the quality of fonts designed for a specific regacy charset > were far better than so-called Unicode fonts even for non-Han charaters. > So, the charset information for non-Han charsets did have some meaning. > But, I don't know the current situation. Perhaps, it is good to remove > them and wait for complaint from users. Thanks. What about using the charset information in general for font selection? Do you think this is a valuable feature, or was it again designed only due to the issues you mention above with fonts designed for legacy charsets?