all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: rms@gnu.org
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: Grammar checking
Date: Sun, 23 Apr 2023 10:14:36 -0400	[thread overview]
Message-ID: <CAM=F=bAC8QTqOAoc55ghjwHybPTqSuVcHFgEeT=fst+9AOP8_w@mail.gmail.com> (raw)
In-Reply-To: <E1pq2t5-0006ar-0c@fencepost.gnu.org>

On Fri, Apr 21, 2023 at 10:22 PM Richard Stallman <rms@gnu.org> wrote:
>   > There's this directory in languagetool's source code that appears to
>   > provide infrastructure for using some RPC protocol for "MLServer"s:
>   > https://github.com/languagetool-org/languagetool/tree/master/languagetool-core/src/main/java/org/languagetool/rules/ml.
>
> If we wamt to use the free version of Languagetool, this raiss
> important questions.  First of all, does the program as currently
> released try by default to use tha remote protocol?
>
[From subsequent amending email]
>   > Secondarily, how much of the usefulness of that program as
>   > currently released is due to using that dis-service?  And how
>   > would we modify the release to turn that off?
>
> If the program as currently released does NOT try ny default to use
> tha protocol, is there something that they invite users to do so as
> to start using it?  We might want to delete that feature from the version
> we distribute, so we don't end up distributing SaaSS unknowingly.
>

The only concrete description I recall seeing (from an emacs user) is
from Ihor Radchenko in
https://lists.gnu.org/archive/html/emacs-devel/2023-03/msg01044.html

The design of the software reflects its intended use in a multi-user
SaaSS server.  If emacs maintainer time is going to be consumed by
ensuring an acceptable version and configuration is installed on user
machines, I hope some consideration (by that maintainer) would be
whether the bulk of the functionality could be implemented in a
simpler, single-user, form in some incremental way - say by an emacs
lisp program running in a batch emacs process.
https://dev.languagetool.org/languages classifies the rules enforced
by LanguageTool into XML, Java-based, spell-checking, and confusion
pairs.  There's a separate 8GB of n-gram data, covering the languages
supported by the languagetool organization.  So, how much work would
be required to meaningfully use the confusion pairs, and what would it
provide.  Or interpreting and applying the XML rules.  Or be more
efficient in the use of the 8GB of n-gram data
(https://dev.languagetool.org/finding-errors-using-n-gram-data).

Maybe the effort wouldn't be worth it, but maybe it would.  I don't
think it's obvious either way.

Lynn



  parent reply	other threads:[~2023-04-23 14:14 UTC|newest]

Thread overview: 128+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  3:00 jinx Richard Stallman
2023-03-29  9:02 ` jinx Philip Kaludercic
2023-03-31  4:29   ` jinx Richard Stallman
2023-03-31  7:15     ` jinx Philip Kaludercic
2023-04-01  3:11       ` jinx Richard Stallman
2023-04-01  6:01         ` jinx Eli Zaretskii
2023-04-01 12:43           ` jinx Peter Oliver
2023-04-01 13:02             ` jinx Eli Zaretskii
2023-04-01 13:21               ` jinx Peter Oliver
2023-04-01  8:54         ` jinx Augusto Stoffel
2023-03-29 22:46 ` jinx Michael Eliachevitch
2023-03-30  1:02   ` jinx João Pedro
2023-03-30  5:23   ` jinx Eli Zaretskii
2023-03-31  4:29   ` jinx Richard Stallman
2023-03-31  6:51     ` jinx Eli Zaretskii
2023-03-31  7:10       ` jinx Gregory Heytings
2023-03-31  7:15         ` Grammar checking (was: jinx) Eli Zaretskii
2023-03-31  7:47           ` Grammar checking Philip Kaludercic
2023-03-31  8:09             ` Gregory Heytings
2023-03-31  8:38               ` Philip Kaludercic
2023-03-31  9:02                 ` Gregory Heytings
2023-03-31 11:37               ` Lynn Winebarger
2023-03-31 12:01                 ` Gregory Heytings
2023-03-31 12:45                   ` Peter Oliver
2023-03-31 15:29                     ` Philip Kaludercic
2023-03-31 17:00                       ` Peter Oliver
2023-03-31 12:54               ` Peter Oliver
2023-03-31 13:09                 ` Gregory Heytings
2023-03-31 11:23             ` Eli Zaretskii
2023-03-31 12:12               ` Peter Oliver
2023-03-31 15:25               ` Philip Kaludercic
2023-03-31  8:40           ` Nasser Alkmim
2023-03-31  8:45             ` Michael Eliachevitch
2023-03-31 13:44               ` Felician Nemeth
2023-03-31 16:03               ` Peter Oliver
2023-03-31  8:48             ` Gregory Heytings
2023-04-01 12:59               ` Lynn Winebarger
2023-04-01 13:18                 ` Gregory Heytings
2023-04-01 13:37                 ` Eli Zaretskii
2023-04-01 17:30                   ` Lynn Winebarger
2023-04-01 17:35                     ` Eli Zaretskii
2023-04-02  3:12                 ` Richard Stallman
2023-04-02 15:24                   ` Lynn Winebarger
2023-04-03  3:05                     ` Richard Stallman
2023-04-03  3:05                     ` Richard Stallman
2023-04-06 12:29                       ` Lynn Winebarger
2023-04-08  3:28                         ` Richard Stallman
2023-04-08 13:33                           ` Lynn Winebarger
2023-04-08 13:23                             ` Eli Zaretskii
2023-04-08  3:28                         ` Richard Stallman
2023-04-08 14:23                           ` Lynn Winebarger
2023-04-08  3:28                         ` Richard Stallman
2023-04-08 15:20                           ` Lynn Winebarger
2023-04-19  5:13                             ` Richard Stallman
2023-04-09  9:02                           ` Philip Kaludercic
2023-04-09 12:31                             ` Lynn Winebarger
2023-04-22  2:22                               ` Richard Stallman
2023-04-23  2:25                                 ` Richard Stallman
2023-04-23 14:14                                 ` Lynn Winebarger [this message]
2023-03-31 10:59             ` Eli Zaretskii
2023-04-02  3:11               ` Richard Stallman
2023-04-02  3:40                 ` Emanuel Berg
2023-03-31 16:20           ` Grammar checking (was: jinx) João Távora
2023-04-05 13:05         ` jinx Rudolf Adamkovič
2023-04-05 18:37           ` jinx Philip Kaludercic
2023-03-31 18:33       ` jinx Arash Esbati
2023-03-31 19:11         ` jinx Eli Zaretskii
2023-03-31 19:35           ` jinx Arash Esbati
2023-04-01  7:20             ` jinx Eli Zaretskii
2023-04-01  7:42               ` jinx Arash Esbati
2023-04-01  8:13                 ` jinx Eli Zaretskii
2023-04-02 11:29                   ` jinx Arash Esbati
2023-04-03 12:32                   ` jinx Michael Heerdegen
2023-04-03 13:51                     ` jinx Michael Eliachevitch
2023-04-03 14:26                     ` jinx Eli Zaretskii
2023-04-03 15:13                       ` jinx Michael Eliachevitch
2023-04-04  2:56                         ` jinx Richard Stallman
2023-04-04 12:27                           ` jinx Michael Heerdegen
2023-04-05  2:35                             ` jinx Richard Stallman
2023-04-05  9:02                               ` jinx Philip Kaludercic
2023-04-05 10:51                                 ` jinx Michael Heerdegen
2023-04-05 11:25                                   ` jinx Michael Heerdegen
2023-04-05 11:55                                     ` jinx Eli Zaretskii
2023-04-05 13:17                                       ` jinx Michael Heerdegen
2023-04-05  2:34                           ` jinx Richard Stallman
2023-04-05  7:58                             ` jinx Po Lu
2023-04-05  8:01                             ` jinx Arash Esbati
2023-04-05  8:15                               ` jinx Emanuel Berg
2023-04-01 13:11               ` jinx Lynn Winebarger
2023-04-01  8:32             ` jinx Augusto Stoffel
2023-04-01  8:29         ` jinx Augusto Stoffel
2023-04-01 11:21           ` jinx Eli Zaretskii
2023-04-01 11:39             ` jinx Augusto Stoffel
2023-04-01 11:54               ` jinx Eli Zaretskii
2023-04-01 12:32                 ` jinx Augusto Stoffel
2023-04-01 12:57                   ` jinx Eli Zaretskii
2023-04-01  3:11       ` jinx Richard Stallman
2023-04-01  5:56         ` jinx Eli Zaretskii
2023-04-01  8:35           ` jinx Augusto Stoffel
2023-04-01  8:25       ` jinx Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2023-03-31  7:46 Grammar checking Payas Relekar
2023-03-31 11:20 ` Eli Zaretskii
2023-03-31 12:55   ` Ihor Radchenko
2023-03-31 13:11     ` Eli Zaretskii
2023-03-31 13:29       ` Ihor Radchenko
2023-03-31 14:19         ` Eli Zaretskii
2023-04-02  3:11       ` Richard Stallman
2023-03-31 12:59   ` Gregory Heytings
2023-03-31 13:20     ` Eli Zaretskii
2023-03-31 13:59       ` Gregory Heytings
2023-03-31 14:28         ` Eli Zaretskii
2023-03-31 14:24       ` Ihor Radchenko
2023-03-31 14:39         ` Eli Zaretskii
2023-04-01  6:52           ` Ihor Radchenko
2023-04-01  7:00             ` Eli Zaretskii
2023-04-01  7:10               ` Ihor Radchenko
2023-04-01  7:14                 ` Eli Zaretskii
2023-04-01 13:09             ` Peter Oliver
2023-04-01 13:17               ` Ihor Radchenko
2023-04-01 13:24                 ` Peter Oliver
2023-04-01 13:32                   ` Ihor Radchenko
2023-04-01 13:42                     ` Eli Zaretskii
2023-04-01 13:41                   ` Eli Zaretskii
2023-04-03 13:02                     ` Peter Oliver
2023-03-31 10:03 Payas Relekar
2023-04-03  5:52 grammar checking Pedro Andres Aranda Gutierrez
2023-04-03 13:51 ` Eli Zaretskii
2023-04-03 15:01   ` Pedro Andres Aranda Gutierrez

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='CAM=F=bAC8QTqOAoc55ghjwHybPTqSuVcHFgEeT=fst+9AOP8_w@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    --cc=rms@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.