all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 1fea9adf520: Improve support for Tifinagh
Date: Mon, 15 Jul 2024 14:06:39 +0300	[thread overview]
Message-ID: <86ikx6j4n4.fsf@gnu.org> (raw)
In-Reply-To: <874j8rdl3z.fsf@gmail.com> (message from Robert Pluim on Mon, 15 Jul 2024 12:07:28 +0200)

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Mon, 15 Jul 2024 12:07:28 +0200
> 
> >>>>> On Sun, 14 Jul 2024 14:21:36 -0400 (EDT), Eli Zaretskii <eliz@gnu.org> said:
> 
> 
>     Eli> diff --git a/lisp/international/fontset.el b/lisp/international/fontset.el
>     Eli> index 33e444507c4..a6129cbc8f0 100644
>     Eli> --- a/lisp/international/fontset.el
>     Eli> +++ b/lisp/international/fontset.el
>     Eli> @@ -199,6 +199,7 @@
>     Eli>          (tai-tham #x1A20 #x1A55 #x1A61 #x1A80)
>     Eli>  	(symbol . [#x201C #x2200 #x2500])
>     Eli>  	(braille #x2800)
>     Eli> +        (tifinagh #x2D30 #x2D60)
>     Eli>  	(ideographic-description #x2FF0)
> 
> Doesnʼt tifinagh cover 2D30..2D7F?

It does.  But if you thought the above implies 2D30..2D60, then it
doesn't: I made the change in script-representative-chars, where these
codepoints have a different interpretation.  See the doc string of
that variable for the details.



  reply	other threads:[~2024-07-15 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172098129645.10577.370472685543343793@vcs2.savannah.gnu.org>
     [not found] ` <20240714182137.51B1FC2BC7E@vcs2.savannah.gnu.org>
2024-07-15 10:07   ` master 1fea9adf520: Improve support for Tifinagh Robert Pluim
2024-07-15 11:06     ` Eli Zaretskii [this message]
2024-07-15 12:19       ` Robert Pluim

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86ikx6j4n4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.