From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Payas Relekar <relekarpayas@gmail.com>,
rms@gnu.org, m.eliachevitch@posteo.de, emacs-devel@gnu.org
Subject: Re: Grammar checking
Date: Fri, 31 Mar 2023 12:59:05 +0000 [thread overview]
Message-ID: <58158ae4984ea8345733@heytings.org> (raw)
In-Reply-To: <838rfd2mmf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
>
> We need in Emacs a free grammar checker that really is up to the job,
> not just any free program. The result should be Emacs features that we
> can be proud of.
>
It's clearly not as accurate as non-free grammar checkers, but it does a
reasonable job. I don't know if that's enough to be proud of it. To give
you a feeling of what it does, I attach the 18 potential grammar errors it
detects in CONTRIBUTE.
[-- Attachment #2: CONTRIBUTE.txt --]
[-- Type: text/plain, Size: 7419 bytes --]
1.) Line 12, column 1, Rule ID: MISSING_GENITIVE[2] premium: false prio=-1
Message: The genitive (âs or sâ) may be missing.
Suggestion: Emacs' development; Emacs's development
...s)Contributing"'.) ** The Emacs repository Emacs development uses Git on Savannah for its main repository...
^^^^^^^^^^^^^^^^^
More info: https://www.ef.edu/english-resources/english-grammar/forming-possessive/
2.) Line 16, column 27, Rule ID: LC_AFTER_PERIOD[1] premium: false
Message: If a new sentence starts here, add a space and start with an uppercase letter.
Suggestion: Email; email
...r.name 'Your Name' git config --global user.email 'your.name@example.com' git config --global...
^^^^^
3.) Line 85, column 27, Rule ID: UPPERCASE_SENTENCE_START premium: false
Message: This sentence does not start with an uppercase letter.
Suggestion: Bug
...cs-devel@gnu.org. ** Issue tracker (a.k.a. "bug tracker") The Emacs issue tracker at https:...
^^^
More info: https://languagetool.org/insights/post/spelling-capital-letters/
4.) Line 113, column 44, Rule ID: ALLOW_TO[1] premium: false
Message: Did you mean âreadingâ? Or maybe you should add a pronoun? In active voice, âallowâ + âtoâ takes an object, usually a pronoun.
Suggestion: reading
...y and takes just one line -- this will allow to read NEWS in Outline mode after hiding the body o...
^^^^^^^
More info: http://www.ef.com/english-resources/english-grammar/gerund-equals-infinitive/
5.) Line 126, column 1, Rule ID: SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA[1] premium: false
Message: A comma may be missing after the conjunctive/linking adverb âOtherwiseâ.
Suggestion: Otherwise,
... those by others, mark the entry with "+++". Otherwise do not mark it. If your change requires upd...
^^^^^^^^^
More info: https://languagetool.org/insights/post/linking-words/
6.) Line 156, column 31, Rule ID: EN_UNPAIRED_BRACKETS premium: false prio=-1
Message: Unpaired symbol: â"â seems to be missing
...mark it in its 'ert-deftest' definition with ":tags '(:expensive-test)". To run tests on t...
^
More info: https://languagetool.org/insights/post/punctuation-guide/#what-are-parentheses
7.) Line 156, column 38, Rule ID: EN_UNPAIRED_BRACKETS premium: false prio=-1
Message: Unpaired symbol: â'â seems to be missing
... in its 'ert-deftest' definition with ":tags '(:expensive-test)". To run tests on the enti...
^
More info: https://languagetool.org/insights/post/punctuation-guide/#what-are-parentheses
8.) Line 198, column 47, Rule ID: NEEDNT_TO_DO_AND_DONT_NEED_DO[3] premium: false
Message: Did you mean âto separateâ?
Suggestion: to separate
... Use this for minor commits that do not need separate ChangeLog entries, such as changes in etc/...
^^^^^^^^
9.) Line 233, column 15, Rule ID: CONFUSION_RULE_GNU_KNEW premium: false prio=-20
Message: âgnuâ (large African antelope) seems less likely than âknewâ (past of âknowâ).
Suggestion: knew
...http: when either will do. In particular, gnu.org and fsf.org URLs should start with "http...
^^^
10.) Line 240, column 53, Rule ID: COMMA_PARENTHESIS_WHITESPACE premium: false
Message: Donât put a space on both sides of a quote symbol.
Suggestion: " ; "
...ines of the commit message that start with "; " are omitted from the generated ChangeLog. ...
^^^
11.) Line 343, column 8, Rule ID: PLUS_MINUS[2] premium: false
Message: Replace by the typographical symbol.
Suggestion: ±
...etters, digits, and characters of the set [-+./_]; - the changes don't include unresolved ...
^^
12.) Line 347, column 15, Rule ID: EN_A_VS_AN premium: false prio=-1
Message: Use âanâ instead of âaâ if the following word starts with a vowel sound, e.g. âan articleâ, âan hourâ.
Suggestion: an
...space characters, and indented lines where a SPC character is immediately followed by a T...
^
More info: https://languagetool.org/insights/post/indefinite-articles/
13.) Line 402, column 53, Rule ID: FOR_WHATEVER_REASONS[1] premium: false
Message: This idiom is spelled with the singular form âreasonâ.
Suggestion: for whatever reason
...anges should not be merged to master at all, for whatever reasons. These should be marked by including someth...
^^^^^^^^^^^^^^^^^^^^
More info: https://www.merriam-webster.com/dictionary/for%20whatever%20reason
14.) Line 411, column 45, Rule ID: CONSECUTIVE_SPACES[1] premium: false
Message: It seems like there are too many consecutive spaces here.
Suggestion:
... group, its own development conventions, etc. The upstream project's code is periodically m...
^^
15.) Line 438, column 1, Rule ID: UPPERCASE_SENTENCE_START premium: false
Message: This sentence does not start with an uppercase letter.
Suggestion: Or
...al/html_node/elisp/GNU-Emacs-Internals.html or run 'info "(elisp)Tips"' or 'info "(elisp)GN...
^^
More info: https://languagetool.org/insights/post/spelling-capital-letters/
16.) Line 452, column 35, Rule ID: COMMA_PARENTHESIS_WHITESPACE premium: false
Message: Donât put a space before the full stop.
Suggestion: .
...directory See all the files in admin/notes/* . In particular, see admin/notes/newfile, see...
^^
17.) Line 499, column 22, Rule ID: COMMA_PARENTHESIS_WHITESPACE premium: false
Message: Donât put a space after the opening parenthesis.
Suggestion: [
...ariables: mode: outline paragraph-separate: "[ \f]*$" coding: utf-8 end:
^^
18.) Line 499, column 25, Rule ID: COMMA_PARENTHESIS_WHITESPACE premium: false
Message: Donât put a space before the closing parenthesis.
Suggestion: ]
...ables: mode: outline paragraph-separate: "[ \f]*$" coding: utf-8 end:
^^
Time: 6302ms for 202 sentences (32.1 sentences/sec)
next prev parent reply other threads:[~2023-03-31 12:59 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
2023-03-31 10:03 Grammar checking Payas Relekar
2023-03-29 3:00 jinx Richard Stallman
2023-03-29 22:46 ` jinx Michael Eliachevitch
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 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
2023-04-08 3:28 ` Richard Stallman
2023-04-08 14:23 ` Lynn Winebarger
2023-03-31 10:59 ` Eli Zaretskii
2023-04-02 3:11 ` Richard Stallman
2023-04-02 3:40 ` Emanuel Berg
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=58158ae4984ea8345733@heytings.org \
--to=gregory@heytings.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=m.eliachevitch@posteo.de \
--cc=relekarpayas@gmail.com \
--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.