From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Add an option to not reduce vocabulary of the Japanese Date: Sat, 04 Jun 2022 20:03:47 +0300 Message-ID: <834k10bbt8.fsf@gnu.org> References: <87r146o2rt.fsf@taiju.info> <8335gme0ml.fsf@gnu.org> <87a6auz1p4.fsf@taiju.info> <83pmjqc89p.fsf@gnu.org> <87sfolwyzj.fsf@taiju.info> <83ee04bz70.fsf@gnu.org> <87h750tzwh.fsf@taiju.info> <83bkv8bl2p.fsf@gnu.org> <87h750e63f.fsf@taiju.info> <835ylgbckg.fsf@gnu.org> <878rqce51u.fsf@taiju.info> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11905"; mail-complaints-to="usenet@ciao.gmane.io" Cc: handa@gnu.org, emacs-devel@gnu.org To: Taiju HIGASHI Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 04 19:05:15 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nxXD9-0002p3-4a for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Jun 2022 19:05:15 +0200 Original-Received: from localhost ([::1]:57444 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nxXD7-0001KN-Ao for ged-emacs-devel@m.gmane-mx.org; Sat, 04 Jun 2022 13:05:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40092) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nxXBw-0008R2-Pe for emacs-devel@gnu.org; Sat, 04 Jun 2022 13:04:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55256) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nxXBw-0007od-GB; Sat, 04 Jun 2022 13:04:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=UP1UnSPaw0SyCo/tzBueSUjwBp94yw9kxNHV8hlFEpQ=; b=GIQxumgDFRRfF9tZVrSk Dschi/YEJVvfSizwkvJ7rBNK0kkOi+8EjiYSH8+Sv7Obwad08rgz2vv/RO6PbJaT98OufHTYEhOaF 9MeMGcsiphRbvXvw/vBukQeTcu8c0dw5dDK2VzOpjbFH/XFzAS78g9K/wPjbkeCni+C+JXuPaSivH ppqku3bVuyFu6ggnByrC/emhDV7VewuCycIgnjI2GJ+hhQgCItxAsuklMkLppRhU0ajHGPnSb+Cw1 yKcc7Uxahd0lmj5+7ptgvd+AY+sa4+Sx0yid+XqLQH0xUzHBmX9x50KCWGcMlkI+Q9pHoF76Fw9Tw 2laDihHhIepvhQ==; Original-Received: from [87.69.77.57] (port=1918 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nxXBv-0008Ik-Vu; Sat, 04 Jun 2022 13:04:00 -0400 In-Reply-To: <878rqce51u.fsf@taiju.info> (message from Taiju HIGASHI on Sun, 05 Jun 2022 02:01:33 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:290669 Archived-At: > From: Taiju HIGASHI > Cc: handa@gnu.org, emacs-devel@gnu.org > Date: Sun, 05 Jun 2022 02:01:33 +0900 > > > >> From: Taiju HIGASHI > >> Cc: handa@gnu.org, emacs-devel@gnu.org > >> Date: Sun, 05 Jun 2022 01:39:00 +0900 > >> > >> > >> > So no separate rules should be necessary. > >> I see. If that is the case, then the v1 patch may be sufficient. With > >> the current rules, the dictionary file has to be deleted beforehand by a > >> gen-clean rule or something to regenerate it, but should I add a rule to > >> force regeneration even if the dictionary file has already been > >> generated? > >> > >> Sorry for my lack of understanding :’( > > > > It is I who should be apologizing for my inability to explain myself > > clearly. > > Then, based on the v1 patch, I will wait for Handa-san's review and then > I will make the final patch. > Is this policy correct? Yes, thanks. We also wait for your paperwork (which already started) to be completed.