unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: handa@gnu.org (K. Handa)
To: Eli Zaretskii <eliz@gnu.org>
Cc: mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: admin/unidata updates
Date: Thu, 26 Jun 2014 23:03:48 +0900	[thread overview]
Message-ID: <87vbrnsr7f.fsf@gnu.org> (raw)
In-Reply-To: <834mz8rkix.fsf@gnu.org> (message from Eli Zaretskii on Wed, 25 Jun 2014 20:01:10 +0300)

In article <834mz8rkix.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> How does one know whether a given script needs CTL?

If a script requires CTL, I think that the section of that
script in The Unicode Standard should contain some
information.

> The practical issue here is whether scripts added to characters.el
> (because the Unicode Standard added them) should also be added to the
> list of "simple scripts" in setup-default-fontset.

As I wrote, adding them without specifying representative
characters is useless.  But, as I have no knowledge about
recently added scripts, I can't provide such information.
So, let's leave the code of setup-default-fontset untouched.

---
Kenichi Handa
handa@gnu.org



  reply	other threads:[~2014-06-26 14:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21 22:10 admin/unidata updates Glenn Morris
2014-06-22 18:53 ` Eli Zaretskii
2014-06-22 23:59   ` Glenn Morris
2014-06-23  2:42     ` Eli Zaretskii
2014-06-23  6:08       ` Glenn Morris
2014-06-23 14:55         ` Eli Zaretskii
2014-06-23 15:37           ` Eli Zaretskii
2014-06-23 16:04             ` Glenn Morris
2014-06-23 16:12               ` Eli Zaretskii
2014-06-23 16:33                 ` Stefan Monnier
2014-06-23 19:54             ` Paul Eggert
2014-06-24 16:59               ` Eli Zaretskii
2014-06-25 15:41             ` K. Handa
2014-06-25 17:01               ` Eli Zaretskii
2014-06-26 14:03                 ` K. Handa [this message]
2014-06-26 15:32                   ` Eli Zaretskii
2014-06-28 14:35                     ` K. Handa
2014-06-28 14:45                       ` Eli Zaretskii

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=87vbrnsr7f.fsf@gnu.org \
    --to=handa@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).