From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 20789@debbugs.gnu.org
Subject: bug#20789: Invalid script or charset name: cuneiform-numbers-and-punctuation
Date: Tue, 16 Jun 2015 17:41:36 +0300 [thread overview]
Message-ID: <834mm7ogv3.fsf@gnu.org> (raw)
In-Reply-To: <ozy4jkh58w.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: 20789@debbugs.gnu.org
> Date: Mon, 15 Jun 2015 20:22:07 -0400
>
> Eli Zaretskii wrote:
>
> >> I don't suppose that big list can be auto-generated from the inputs?
> >
> > It's not trivial. I describe below some of the issues, in the hope
> > that Someone™ will volunteer:
>
> Thanks. Script that processes Blocks.txt attached. Some questions:
>
> 1. In Blocks.txt:
>
> FF00..FFEF; Halfwidth and Fullwidth Forms
>
> In Emacs:
>
> (#xFF00 #xFF5F cjk-misc)
> (#xFF61 #xFF9F kana)
> (#xFFE0 #xFFEF cjk-misc)
>
> Is ff60 (FULLWIDTH RIGHT WHITE PARENTHESIS) intentionally omitted?
AFAICT, there's a small mess around there. Based on the names of the
pertinent characters, I think we should have this instead of the above
3 ranges:
(#xFF00 #xFF60 cjk-misc)
(#xFF61 #xFF9F kana)
(#xFFA0 #xFFDF hangul)
(#xFFE0 #xFFEF cjk-misc)
> 2. In Emacs "olt-italic" looks like a typo ("old-italic"). Can it be renamed?
Yes, please.
> 3. In Blocks.txt, Anatolian Hieroglyphs ends at 1467F.
> In Emacs, it ends at 1457F. Typo?
Yes.
> 4. In Blocks.txt:
>
> 20000..2A6DF; CJK Unified Ideographs Extension B
> 2A700..2B73F; CJK Unified Ideographs Extension C
> 2B740..2B81F; CJK Unified Ideographs Extension D
> 2B820..2CEAF; CJK Unified Ideographs Extension E
> 2F800..2FA1F; CJK Compatibility Ideographs Supplement
>
> In Emacs:
>
> (#x20000 #x2CEAF han)
> (#x2F800 #x2FFFF han)
>
> Emacs adds the ranges 2a6e0:2a6ff and 2fa20:2ffff, which Blocks.txt does
> not cover. Intentional?
I don't know, but probably not intentional. I think we had better
made it consistent with the UCD.
> 5. Newly added "sutton-sign-writing" - should be "sutton-signwriting"?
> (The case-insensitive source says "Sutton SignWriting".)
Well, "signwriting" is not a word, AFAIK, it's 2 words (and the funny
camel-case seems to agree with me). AFAIU, they used "SignWriting"
because it's the commercial name. But if you insist, I won't...
Thank you for doing this.
P.S. Does the script work with mawk? (Some systems have it as their
default Awk, I think.)
next prev parent reply other threads:[~2015-06-16 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 22:05 bug#20789: Invalid script or charset name: cuneiform-numbers-and-punctuation Glenn Morris
2015-06-11 22:24 ` Glenn Morris
2015-06-12 8:28 ` Eli Zaretskii
2015-06-16 0:22 ` Glenn Morris
2015-06-16 14:41 ` Eli Zaretskii [this message]
2015-06-17 6:52 ` Glenn Morris
2015-06-17 16:27 ` Eli Zaretskii
2015-06-20 23:34 ` Glenn Morris
2015-06-21 15:00 ` Eli Zaretskii
2015-06-27 2:02 ` Glenn Morris
2015-06-27 7:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834mm7ogv3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20789@debbugs.gnu.org \
--cc=rgm@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 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.