From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: higashi@taiju.info, handa@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Add an option to not reduce vocabulary of the Japanese
Date: Mon, 06 Jun 2022 17:17:33 +0300 [thread overview]
Message-ID: <837d5t98qq.fsf@gnu.org> (raw)
In-Reply-To: <87k09tubfa.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 06 Jun 2022 16:14:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: handa <handa@gnu.org>, eliz@gnu.org, emacs-devel@gnu.org
> Date: Mon, 06 Jun 2022 16:14:01 +0200
>
> Taiju HIGASHI <higashi@taiju.info> writes:
>
> > I have also received a suggestion to make it a run-time option instead
> > of a build-time option, is it possible to get some opinion on that?
> >
> > Because I cannot see how many users would want a dictionary with a reduced
> > vocabulary.
>
> I think if everybody agrees that nobody would want a reduced dictionary,
> then we should just stop reducing the dictionary -- no
> configuration/run-time options necessary.
I think a configuration option, by default off, is a good way of
removing the reduction, but still leaving someone who may want that a
"fire escape". The cost in complexity is quite small in this case.
next prev parent reply other threads:[~2022-06-06 14:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 3:16 [PATCH] Add an option to not reduce vocabulary of the Japanese Taiju HIGASHI
2022-06-03 6:12 ` Eli Zaretskii
2022-06-03 6:43 ` Taiju HIGASHI
2022-06-03 11:10 ` Eli Zaretskii
[not found] ` <87sfolwyzj.fsf@taiju.info>
2022-06-04 8:38 ` Eli Zaretskii
2022-06-04 11:46 ` Taiju HIGASHI
2022-06-04 13:43 ` Eli Zaretskii
2022-06-04 16:39 ` Taiju HIGASHI
2022-06-04 16:47 ` Eli Zaretskii
2022-06-04 17:01 ` Taiju HIGASHI
2022-06-04 17:03 ` Eli Zaretskii
2022-06-05 3:05 ` handa
2022-06-05 14:07 ` Taiju HIGASHI
2022-06-06 11:52 ` handa
2022-06-06 12:53 ` Taiju HIGASHI
2022-06-06 14:14 ` Lars Ingebrigtsen
2022-06-06 14:17 ` Eli Zaretskii [this message]
2022-06-06 15:08 ` Taiju HIGASHI
2022-06-06 16:05 ` Eli Zaretskii
2022-06-07 0:47 ` Taiju HIGASHI
2022-06-07 1:06 ` Taiju HIGASHI
2022-06-07 3:50 ` Taiju HIGASHI
2022-06-07 10:58 ` Eli Zaretskii
2022-06-07 9:36 ` Lars Ingebrigtsen
2022-06-07 10:10 ` Taiju HIGASHI
2022-06-07 10:22 ` Lars Ingebrigtsen
2022-06-07 10:48 ` Eli Zaretskii
2022-06-07 12:12 ` Taiju HIGASHI
2022-06-07 12:41 ` Taiju HIGASHI
2022-06-07 13:08 ` Taiju HIGASHI
2022-06-09 13:10 ` Taiju HIGASHI
2022-06-09 13:14 ` Eli Zaretskii
2022-06-10 13:15 ` Eli Zaretskii
2022-06-10 13:50 ` Taiju HIGASHI
2022-06-03 23:51 ` Richard Stallman
2022-06-04 10:57 ` Taiju HIGASHI
2022-06-04 11:19 ` Taiju HIGASHI
2022-06-05 22:53 ` Richard Stallman
2022-06-06 0:05 ` Taiju HIGASHI
2022-06-03 23:52 ` Richard Stallman
2022-06-04 6:25 ` Eli Zaretskii
2022-06-04 12:36 ` Taiju HIGASHI
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=837d5t98qq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@gnu.org \
--cc=higashi@taiju.info \
--cc=larsi@gnus.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.