From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs release schedule and Akihito's abdication Date: Sat, 28 Jul 2018 10:09:52 +0300 Message-ID: <83muubrg3j.fsf@gnu.org> References: <2de88b1c-f576-d009-80ae-8581227463fa@gmail.com> <6019f365-6417-ac5f-4963-93adadcfe132@cs.ucla.edu> <202d6243-4313-d758-de17-b5c2cc5b69ff@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1532761675 15428 195.159.176.226 (28 Jul 2018 07:07:55 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 28 Jul 2018 07:07:55 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 28 09:07:51 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fjJKQ-0003tp-SB for ged-emacs-devel@m.gmane.org; Sat, 28 Jul 2018 09:07:50 +0200 Original-Received: from localhost ([::1]:44127 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjJMV-0004mT-S8 for ged-emacs-devel@m.gmane.org; Sat, 28 Jul 2018 03:09:59 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44224) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjJMQ-0004mM-9S for emacs-devel@gnu.org; Sat, 28 Jul 2018 03:09:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fjJMN-0001rB-5g for emacs-devel@gnu.org; Sat, 28 Jul 2018 03:09:54 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fjJMN-0001qq-1f; Sat, 28 Jul 2018 03:09:51 -0400 Original-Received: from [176.228.60.248] (port=3975 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fjJMM-0007vp-AE; Sat, 28 Jul 2018 03:09:50 -0400 In-reply-to: <202d6243-4313-d758-de17-b5c2cc5b69ff@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Sat, 28 Jul 2018 01:00:45 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:227900 Archived-At: > From: Clément Pit-Claudel > Date: Sat, 28 Jul 2018 01:00:45 -0400 > > 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 :) I'm not sure it is worth the hassle, but one might go through admin/notes/Unicode, and consider whether any of the stuff we do there when importing a new Unicode version may or may not be affected by this issue. Regardless, we always try to comply to the latest version of the Unicode standard when we release Emacs, so if a draft of Unicode will have existed with the new character by the time we make the release, we could use that.