From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuSBTYW1lZXIgU2luZ2g=?= Newsgroups: gmane.emacs.devel Subject: Re: Supporting stylistic sets Date: Sat, 24 Sep 2022 14:04:42 +0530 Message-ID: References: <83wn9up0es.fsf@gnu.org> <83illeou0j.fsf@gnu.org> <83r101ntwi.fsf@gnu.org> <83illdnpn3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002a2ab805e9682b65" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29080"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 24 10:37:51 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 1oc0fW-0007PR-S9 for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Sep 2022 10:37:50 +0200 Original-Received: from localhost ([::1]:50288 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oc0fV-0005xI-Qc for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Sep 2022 04:37:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oc0cn-0004Ld-09 for emacs-devel@gnu.org; Sat, 24 Sep 2022 04:35:01 -0400 Original-Received: from mail-yb1-xb35.google.com ([2607:f8b0:4864:20::b35]:33578) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oc0ch-0008Pk-6M; Sat, 24 Sep 2022 04:34:59 -0400 Original-Received: by mail-yb1-xb35.google.com with SMTP id p69so2677305yba.0; Sat, 24 Sep 2022 01:34:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Jq+zbpcDT1C1a4QRzcRZNfnUEPXm/g9rUxOqs90hUnM=; b=F8sYEvQKZhNLEPpDTTObVmVbFCySoI0b0O9iHOaSZe4NCjAOUqCR0u8eRW9wniE//b 4eRPXFxX870OY5Eyzu3e08hxaPCvkRhWC6T1RBi3P+pBYBzWOEjsgu+s0KT9RFZd/n3k VrHzgA7H0KSlUw7GDL6mzXxI3QxGuRhAegkYxpQv7P40BoUgJ36d5F4dxBPeW9ZBtGMr IAGiJxh+gI4zJxK0SXOhIV0ORVd+lm2zxWPF5GAK61ZTHewzS6VXkz2dqCxZid6SB4DG +MAA7InJN/hCbMP3NiLm7l3CJcqAfDgCCQH/7EpUUq6+XxTaTaWeh7yLH+BzH1pd8qEE 8jIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Jq+zbpcDT1C1a4QRzcRZNfnUEPXm/g9rUxOqs90hUnM=; b=qsRErSieEgSnc8BGehWCAQh8rME8B44dpS2OoJbnZEYMz+AHJ9TP1luR/v1FD9zjjD ZiNlH4tRHIiOqgLumAARpBSjmEFXk4mqpiNzkRvEMdCrT+M+wPS8DcfS4Xy5qgQKLVmI XYjfiYhOPAUxASQ3DHW7MgdJdbkGgELRJe3FDkyftcp3zfZxxh1y5vkuGneA/K7jrrOj TGBmCXYhJ9yAQkKJ8thI8qJCB1a2fTzi3nAJNEdgF7j8BNshgw3pDsNiXKu7KcTalAtQ KfnKHwfdBJUW3/vhWOj7gDri2u7YFCEAycLXEwW83pCbrfUKTYHXsn2r60HPmgiILAIT L2yA== X-Gm-Message-State: ACrzQf28HVUjpnkfVHtMEzAQ07ZZigOd9OQH+e1nzmzTA8+gveFtlLb/ px9FPkk7NNP1teT9w9/hF+Rh7PutBy9akbQ6BH+TsCfYPCBaGpZQ X-Google-Smtp-Source: AMsMyM5cuwy9xLz09XdzvLF6YWI6R/wz3Dd1jPfFFis27xiEJAihON9PjmsMSHZO8dJ/li8vK+pWjnUR2HvQiD+nSh8= X-Received: by 2002:a25:37ce:0:b0:6b6:41a8:9df with SMTP id e197-20020a2537ce000000b006b641a809dfmr8302218yba.251.1664008493605; Sat, 24 Sep 2022 01:34:53 -0700 (PDT) In-Reply-To: <83illdnpn3.fsf@gnu.org> Received-SPF: pass client-ip=2607:f8b0:4864:20::b35; envelope-from=lumarzeli30@gmail.com; helo=mail-yb1-xb35.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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.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:296130 Archived-At: --0000000000002a2ab805e9682b65 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > Then font-level specification of this would not be as simple as was > originally suggested, I think: the characters were missing from that > suggestion. We don't have to specify each character for which we want the stylistic-set, we just simply would have to pass the tags and hb_shape_full would take care of the rest. On Sat, Sep 24, 2022 at 1:57 PM Eli Zaretskii wrote: > > From: =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4=B0 =E0=A4=B8=E0=A4=BF=E0=A4=82= =E0=A4=B9 Sameer Singh > > Date: Sat, 24 Sep 2022 13:30:00 +0530 > > Cc: emacs-devel@gnu.org > > > > You are thinking about one particular use case. There might be > > others. > > > > What might be the other use cases? > > I don't really know. That was a comment asking for responses from > anyone who could know. > > > Btw, is it always the case that, when using a particular font, users > > will want to apply the same stylistic-set feature to all of the > > characters from the font that have alternative glyphs? If not, then > > font-level feature sets are not going to solve that, and we will need > > to be able to specify this for each character individually. > > > > There are different stylistic-set features for different glyphs. > > For example in FiraCode to change "a" there is cv01, for "g" cv02 etc. > > Then font-level specification of this would not be as simple as was > originally suggested, I think: the characters were missing from that > suggestion. > --0000000000002a2ab805e9682b65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Then fon= t-level specification of this would not be as simple as was
originally suggested, I think: the characters were missing from that
suggestion.

We don't have to specify ea= ch character for which we want the stylistic-set, we just simply would have= to pass the tags
and hb_shape_full would take care of the rest. =

On Sat, Sep 24, 2022 at 1:57 PM Eli Zaretskii <eliz@gnu.org> wrote:
> From: =E0=A4=B8=E0=A4=AE=E0=A5=80=E0=A4= =B0 =E0=A4=B8=E0=A4=BF=E0=A4=82=E0=A4=B9 Sameer Singh <lumarzeli30@gmail.com>
> Date: Sat, 24 Sep 2022 13:30:00 +0530
> Cc: emacs-dev= el@gnu.org
>
>=C2=A0 You are thinking about one particular use case.=C2=A0 There migh= t be
>=C2=A0 others.
>
> What might be the other use cases?

I don't really know.=C2=A0 That was a comment asking for responses from=
anyone who could know.

>=C2=A0 Btw, is it always the case that, when using a particular font, u= sers
>=C2=A0 will want to apply the same stylistic-set feature to all of the<= br> >=C2=A0 characters from the font that have alternative glyphs?=C2=A0 If = not, then
>=C2=A0 font-level feature sets are not going to solve that, and we will= need
>=C2=A0 to be able to specify this for each character individually.
>
> There are different stylistic-set features for different glyphs.
> For example in FiraCode to change "a" there is cv01, for &qu= ot;g" cv02 etc.

Then font-level specification of this would not be as simple as was
originally suggested, I think: the characters were missing from that
suggestion.
--0000000000002a2ab805e9682b65--