I can't see any grammar checking

Checkbox "Parenthesss" in Tools>Options…>Language settings>English sentence checking>Grammar checking is active

"Check grammar as you type" is active in Tools>Options…>Language settings>writing aids>options

Grammar checking works in German (using Language Tool 5.4), but I have not idea, why it doesn't work in English.

I did some more experimenting after reading your comments and discovered something very interesting, if not downright odd.

I now realize that this issue is, at least in part, due to my unchecking the “Check spelling as you type” option in: 

Tools > Options… > Language Settings > Writing Aids > Options.

NOTE: The same thing can be accomplished by simply turning off the “Toggle Automatic Spell Checking (Shift+F7)” feature in the Standard Menu Bar. (So, why have a duplicate feature with a different, albeit similar, name?)

I did this because of the nagging issue LO Writer has of auto-correcting text that is in fact correct as typed; for example, computer code that is not capitalized. Now, one would NOT think that this setting, the “Check spelling as you type” setting, would have anything to do with the issue this bug report was referring to, which is the “Check grammar as you type” setting, but I have just tried numerous times and the grammar (e.g., incorrect capitalization, missing/unpaired quotation marks, and the missing/unpaired parentheses) functions do NOT work unless you also have the “Check spelling as you type” setting checked. That is counterintuitive behavior because spelling and grammar are two completely different subjects, which is why they presumably have two separate check-boxes. Additionally, it makes little sense because there is only a red squiggly underline associated with the “Toggle Automatic Spell Checking” icon in the Standard Menu Bar—not a blue squiggly underline paired with it. 

Example: I wrote the two sentences below with an extra, or missing, punctuation mark. Note: I had both “Toggle Automatic Spell Checking” and “Check spelling as you type” turned off and the “Check grammar as you type” turned on. LO Writer did NOT detect either grammatical error – not what one would expect after turning the grammar checker on.

“Now is the time for all “good men and women” to come to the aid of their country.

“Now is the time for all good men (and women)) to come to the aid of their country.”

I then clicked the “Toggle Automatic Spell Checking” on the Standard Menu Bar to turn it on and it then instantly detected the missing quotation mark in the first sentence but failed to detect the extra, or unpaired, closing parentheses in the second sentence. That is bizarre because both grammar checking functions use the same checkbox (Parentheses) to invoke both functions (parentheses and quotation marks). On the other hand, if you then turn “Check grammar as you type” off, it does not detect either punctuation error – as expected.

The following is a related side note. If you try to check the checkbox for “Check spelling as you type” when the “Toggle Automatic Spell Checking” is NOT selected in the Standard Tool Bar, then when you press “Apply”, the Standard Tool Bar will automatically switch to being selected – but the checkbox for “Check spelling as you type” you just checked will flip back to being unchecked. If you then either close the window, click the “Apply” button a second time, or press “OK”, the two settings will sync back up together. This rather odd behavior is counter-intuitive and unexpected.

Interesting oddity concerning the missing/unpaired parentheses issue. With only one unpaired parentheses in a line of text (see ordered number list item 1) and 2) below), the grammatical checking works. However, when an unpaired parentheses is combined with one or more paired parentheses (see ordered number list item 3)), it does NOT work.

Example:

1) to draw a rectangle, first make a square shape, then press the shift key and drag a side of the square to make a rectangle

2) double click a selection to be able to use it repeatedly without having to re-select it each time

3) to make copies of an object, select it, R-click, Copy, Paste (will paste over top of original, so then move to new location)

A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.

This bug is still present. The Version drop-down list above is only for the earliest affected, but it is still present in 7.4.0.3. Due to that version not remembering to load the program fully maximized on each reload, I had to opt to load 7.4.1.1. The bug is still present in that version as well.

I still can't assess, if this is a bug or a problem with some settings. But I've just recognized, that "English Sentence Checking" is target from options button of "English dictionaries for LibreOffice" extension.

So Marco, perhaps you can give some insights?

cc: Marco A. Pinto

Sorry, too stressed to think.

I tested this by installing LanguageTool 6.0 and using English (USA) https://extensions.libreoffice.org/en/extensions/show/languagetool

(In reply to Eek! A Bug. Kill it! from comment #2)
> I then clicked the “Toggle Automatic Spell Checking” on the Standard Menu
> Bar to turn it on and it then instantly detected the missing quotation mark
> in the first sentence but failed to detect the extra, or unpaired, closing
> parentheses in the second sentence. That is bizarre because both grammar
> checking functions use the same checkbox (Parentheses) to invoke both
> functions (parentheses and quotation marks). On the other hand, if you then
> turn “Check grammar as you type” off, it does not detect either punctuation
> error – as expected.

The extra parenthesis is detected correctly both automatically and in Spelling dialog.

(In reply to Eek! A Bug. Kill it! from comment #3)
> Interesting oddity concerning the missing/unpaired parentheses issue. With
> only one unpaired parentheses in a line of text (see ordered number list
> item 1) and 2) below), the grammatical checking works. However, when an
> unpaired parentheses is combined with one or more paired parentheses (see
> ordered number list item 3)), it does NOT work.

Even this double extra parenthesis is detected.

However, I noticed that there is some "instability" in the rendering of the blue underline. First, it takes a couple of seconds to appear. Then, if you type something, it disappears again for a while. Finally, it disappeared at one point even when I was not doing anything.

The blue underline was stable most of the time, though.

Arch Linux 64-bit, X11
Version: 7.5.0.3 (X86_64) / LibreOffice Community
Build ID: 50(Build:3)
CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb)
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
7.5.0-1
Calc: threaded

Eek! A Bug. Kill it! Could you please retest with new 24.2 version of LO? Please also comment on comment 8. Thank you.
=> NEEDINFO

Dear Eek! A Bug. Kill it!,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp