unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
Cc: 58098@debbugs.gnu.org
Subject: bug#58098: Improve composition rules for Gumrukhi
Date: Tue, 27 Sep 2022 17:08:12 +0300	[thread overview]
Message-ID: <831qrwkj03.fsf@gnu.org> (raw)
In-Reply-To: <CAOR1sLzBqx4Ya99B55WsCM+YY0kE1x7z_0ekdASmGDJwcsdDjQ@mail.gmail.com> (message from समीर सिंह Sameer Singh on Tue, 27 Sep 2022 19:22:09 +0530)

> From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> Date: Tue, 27 Sep 2022 19:22:09 +0530
> Cc: 58098@debbugs.gnu.org
> 
>  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.

The form

       (chess-symbol #x1FA00 #x1FA67)

requires that _both_ #x1FA00 and #x1FA67 be supported by a font, for
it to be eligible to display chess-symbols.  By contrast, the form

       (chess-symbol . [#x1FA00 #x1FA67])

requires that _either_ of the two characters is supported.  So my
question is: do we really want _both_ of the characters supported by a
font, and if not, do we really want Emacs to reject such a font?

Did you look at what #x1FA67 looks like?  It is not a "traditional"
chess symbol.  And neither are the characters that are its neighbors.

>  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) 

You don't have Symbola installed?





  reply	other threads:[~2022-09-27 14:08 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
2022-09-27 14:08         ` Eli Zaretskii [this message]
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=831qrwkj03.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58098@debbugs.gnu.org \
    --cc=lumarzeli30@gmail.com \
    /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).