From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Supporting stylistic sets
Date: Sat, 24 Sep 2022 19:56:47 +0530 [thread overview]
Message-ID: <CAOR1sLwStriXSDXqQXZHhbQHtM+enWQc7ZTH10WWSDH=M-zcog@mail.gmail.com> (raw)
In-Reply-To: <837d1sonyc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
Simply pass both of their tags to hb_shape_full, which I think would be
done something like this:
hb_feature_t features[] = {{HB_TAG("c","v","0","6"), 1, start, end},
{HB_TAG("c","v","0","8"), 1, start, end}};
hb_shape_full(font, buffer, features, 2, NULL);
On Sat, Sep 24, 2022 at 7:48 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Sat, 24 Sep 2022 18:40:55 +0530
> > Cc: emacs-devel@gnu.org
> >
> > You are suggesting that we let the font and the shaping engine decide
> > which alternative to use? That sounds un-Emacsy to me. For the use
> > case where only specific characters should be affected, I think we
> > should have a facility whereby users could specify, for each character
> > that has alternatives, which one to use.
> >
> > No, I am not suggesting that every variation has its own tag and the
> user can choose which tag they would
> > like or not.
> > For example look at the FiraCode variations attached
>
> So what do I do if I want variant 4 for 'i' and variant 2 for 'l'?
>
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2022-09-24 14:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 12:54 Supporting stylistic sets समीर सिंह Sameer Singh
2022-09-23 15:37 ` Eli Zaretskii
2022-09-23 17:27 ` समीर सिंह Sameer Singh
2022-09-23 17:31 ` Nicolas Ouellet-payeur
2022-09-23 18:09 ` Eli Zaretskii
2022-09-23 19:20 ` Nicolas Ouellet-payeur
2022-09-23 20:10 ` Eli Zaretskii
[not found] ` <CADuLPF5sKi4NMcGSdy1GAi8=KHBfUcVa3tV=XwnhPfWxroAJCA@mail.gmail.com>
2022-09-26 17:07 ` Eli Zaretskii
2022-09-26 17:46 ` Nicolas Ouellet-payeur
2022-09-26 18:28 ` Eli Zaretskii
2022-09-26 19:06 ` Yuri Khan
2022-09-26 19:20 ` Eli Zaretskii
2022-09-23 17:55 ` Eli Zaretskii
2022-09-23 18:26 ` Visuwesh
2022-09-23 18:55 ` Eli Zaretskii
2022-09-24 4:59 ` Visuwesh
2022-09-24 6:33 ` Eli Zaretskii
2022-09-24 8:42 ` Visuwesh
2022-09-24 4:43 ` समीर सिंह Sameer Singh
2022-09-24 6:55 ` Eli Zaretskii
2022-09-24 8:00 ` समीर सिंह Sameer Singh
2022-09-24 8:27 ` Eli Zaretskii
2022-09-24 8:34 ` समीर सिंह Sameer Singh
2022-09-24 8:38 ` Eli Zaretskii
2022-09-24 8:41 ` समीर सिंह Sameer Singh
2022-09-24 8:50 ` समीर सिंह Sameer Singh
2022-09-24 12:09 ` समीर सिंह Sameer Singh
2022-09-24 12:35 ` Eli Zaretskii
2022-09-24 12:45 ` समीर सिंह Sameer Singh
2022-09-24 13:00 ` Eli Zaretskii
2022-09-24 13:10 ` समीर सिंह Sameer Singh
2022-09-24 14:18 ` Eli Zaretskii
2022-09-24 14:26 ` समीर सिंह Sameer Singh [this message]
2022-09-24 15:01 ` Eli Zaretskii
2022-09-24 15:02 ` समीर सिंह Sameer Singh
2022-09-24 15:21 ` Eli Zaretskii
2022-09-24 15:50 ` समीर सिंह Sameer Singh
2022-09-24 16:14 ` Eli Zaretskii
2022-09-24 16:42 ` Yuri Khan
2022-09-24 17:02 ` Eli Zaretskii
2022-09-24 17:09 ` समीर सिंह Sameer Singh
2022-09-24 17:11 ` समीर सिंह Sameer Singh
2022-09-25 22:19 ` Clément Pit-Claudel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOR1sLwStriXSDXqQXZHhbQHtM+enWQc7ZTH10WWSDH=M-zcog@mail.gmail.com' \
--to=lumarzeli30@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).