From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: Emacs release schedule and Akihito's abdication
Date: Sat, 28 Jul 2018 01:00:45 -0400 [thread overview]
Message-ID: <202d6243-4313-d758-de17-b5c2cc5b69ff@gmail.com> (raw)
In-Reply-To: <6019f365-6417-ac5f-4963-93adadcfe132@cs.ucla.edu>
On 2018-07-27 19:41, Paul Eggert wrote:
> Clément Pit-Claudel wrote:
>> Can you clarify how Japanese text would break?
>
> Sorry, I don't know exactly. One thing is that the regular expression [[:alpha:]] wouldn't match the new character even though it'll be alphabetic. Although I expect more issues will arise, not being a heavy-duty Japanese user I don't know what they'll be.
Thanks. Maybe someone else on the list will have further insight :)
> From the Unicode point of view, the issue is not merely assigning a code point for the new character (that's already done: it'll be U+32FF)
Indeed (I read your two links with great interest, and these issues were what I alluded to in mentioning C-u x =). The point about [[:alpha:]] is a good one. If it's the only issue, maybe we could save an extra release by ensuring that [:alpha:] includes U+32FF (we don't need to know what U+32FF will look like to add it to the appropriate regex class).
As I mentioned earlier, this is mostly curiosity :)
Clément.
next prev parent reply other threads:[~2018-07-28 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 20:20 Emacs release schedule and Akihito's abdication Paul Eggert
2018-07-27 20:35 ` John Wiegley
2018-07-27 21:17 ` Eli Zaretskii
2018-07-27 23:36 ` Paul Eggert
2018-07-27 21:38 ` Clément Pit-Claudel
2018-07-27 23:41 ` Paul Eggert
2018-07-28 5:00 ` Clément Pit-Claudel [this message]
2018-07-28 7:09 ` Eli Zaretskii
2018-07-28 11:08 ` Van L
2018-07-28 20:53 ` Paul Eggert
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=202d6243-4313-d758-de17-b5c2cc5b69ff@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).