From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58098@debbugs.gnu.org
Subject: bug#58098: Improve composition rules for Gumrukhi
Date: Tue, 27 Sep 2022 19:22:09 +0530 [thread overview]
Message-ID: <CAOR1sLzBqx4Ya99B55WsCM+YY0kE1x7z_0ekdASmGDJwcsdDjQ@mail.gmail.com> (raw)
In-Reply-To: <834jwtj6zq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]
>
> I don't understand this part: why should we require #x1FA67? Did you
> perhaps mean this:
>
> (chess-symbol . [#x1FA00 #x1FA67])
Isn't the script-representative-chars used to improve font selection by
requesting more characters?
So does the specific character requested have any effect? because I chose
it randomly.
We already have the setup for chess-symbol, below this line where you
> are making changes. Is it not enough for some reason?
>
Prior to this patch the chess symbol block was not rendered on my machine
despite having its font (Noto Sans Symbols2)
On Tue, Sep 27, 2022 at 6:43 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: समीर सिंह Sameer Singh
> > <lumarzeli30@gmail.com>
> > Date: Tue, 27 Sep 2022 01:30:31 +0530
> >
> > --- a/lisp/international/fontset.el
> > +++ b/lisp/international/fontset.el
> > @@ -300,7 +300,8 @@ font-encoding-charset-alist
> > (ottoman-siyaq-number #x1ed01)
> > (mahjong-tile #x1F000)
> > (domino-tile #x1F030)
> > - (emoji #x1F300 #x1F600)))
> > + (emoji #x1F300 #x1F600)
> > + (chess-symbol #x1FA00 #x1FA67)))
>
> I don't understand this part: why should we require #x1FA67? Did you
> perhaps mean this:
>
> (chess-symbol . [#x1FA00 #x1FA67])
>
> > @@ -836,7 +837,8 @@ setup-default-fontset
> > tai-tham
> > mahjong-tile
> > domino-tile
> > - emoji))
> > + emoji
> > + chess-symbol))
>
> We already have the setup for chess-symbol, below this line where you
> are making changes. Is it not enough for some reason?
>
[-- Attachment #2: Type: text/html, Size: 2621 bytes --]
next prev parent reply other threads:[~2022-09-27 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:43 bug#58098: Improve composition rules for Gumrukhi समीर सिंह Sameer Singh
2022-09-26 18:47 ` समीर सिंह Sameer Singh
2022-09-26 20:00 ` समीर सिंह Sameer Singh
2022-09-27 13:12 ` Eli Zaretskii
2022-09-27 13:52 ` समीर सिंह Sameer Singh [this message]
2022-09-27 14:08 ` Eli Zaretskii
2022-09-27 15:24 ` समीर सिंह Sameer Singh
2022-09-28 12:39 ` Eli Zaretskii
2022-09-28 12:57 ` समीर सिंह Sameer Singh
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=CAOR1sLzBqx4Ya99B55WsCM+YY0kE1x7z_0ekdASmGDJwcsdDjQ@mail.gmail.com \
--to=lumarzeli30@gmail.com \
--cc=58098@debbugs.gnu.org \
--cc=eliz@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).