From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Supporting stylistic sets Date: Sat, 24 Sep 2022 20:02:32 +0300 Message-ID: <83wn9sn1sn.fsf@gnu.org> References: <83wn9up0es.fsf@gnu.org> <83illeou0j.fsf@gnu.org> <83r101ntwi.fsf@gnu.org> <83illdnpn3.fsf@gnu.org> <83h70xnp43.fsf@gnu.org> <83bkr5ne65.fsf@gnu.org> <83a66pnczg.fsf@gnu.org> <837d1sonyc.fsf@gnu.org> <834jwwolyz.fsf@gnu.org> <8335cgol11.fsf@gnu.org> <83y1u8n414.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33933"; mail-complaints-to="usenet@ciao.gmane.io" Cc: lumarzeli30@gmail.com, emacs-devel@gnu.org To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 24 19:03:53 2022 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 1oc8ZF-0008dG-6a for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Sep 2022 19:03:53 +0200 Original-Received: from localhost ([::1]:51960 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oc8ZD-00022s-NH for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Sep 2022 13:03:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43490) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oc8YA-0001MB-S2 for emacs-devel@gnu.org; Sat, 24 Sep 2022 13:02:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35374) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oc8YA-00085r-FA; Sat, 24 Sep 2022 13:02:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=U7+wQc10J5YLaKiCoTqumx+X0CuHzP0Xz5dOXJPpKPw=; b=XIdPZpdvnbOZESMi/Eo4 7Jkj1un7sArrcYWtH51Y0/O3oAZnc87RPi2KMgR7M4tSxgXuBGYv4CunsgGk29n+Owstp5dkAajEG Xq1xfZQkEdQz6WgtRLbxVeHQN7PIPV1a5szLqGJzY/6nSi1RpdHWKivhB5bHph4HRIeSgdzof5O8J m0KlMuIjR+D0gj2Dakio55rsSvBKdHdLDIRQXxEVOhRqMEXB/uwsFkR25HGOrWmjVXW3eIKABDQmL 6tQEHewTwskRreI7BrAB7led3h3pYbhqRTlqdXLkSBxd+4sH6gSS1EWw/MuQMJDJD2Mluf8FxA2EO cUDYQFloWK0H9A==; Original-Received: from [87.69.77.57] (port=2928 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oc8Y9-0004Hi-RS; Sat, 24 Sep 2022 13:02:46 -0400 In-Reply-To: (message from Yuri Khan on Sat, 24 Sep 2022 23:42:33 +0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:296172 Archived-At: > From: Yuri Khan > Date: Sat, 24 Sep 2022 23:42:33 +0700 > Cc: समीर सिंह Sameer Singh , > emacs-devel@gnu.org > > On Sat, 24 Sept 2022 at 23:15, Eli Zaretskii wrote: > > > I'm sorry, I still don't understand. (I'm not an expert on fonts, so > > I'd appreciate a slightly more detailed explanations.) Are you saying > > that each tag can be used by a single character in a font? IOW, no > > feature tag can ever be shared by two or more characters in a font? > > As I understand it, the font has instructions like “if stylistic set X > is in effect, use glyphs Y1, Y2, …, Yn for characters Z1, Z2, …, Zn”. > Depending on the font designer’s whim, there could be separate > stylistic sets for each character, sets for multiple characters > similar in shape, and/or sets for a group of characters where the user > is unlikely to want to control each character separately. "Unlikely" doesn't fly with Emacs users. Someone will want to do just that. AFAIR, MS Office allows the user to select variants separately for each character. And if we want to support only the "likely" use cases, then the idea of a special text property seems more attractive, since that means entire segments of text will have the same collection of stylistic sets.