Bug 47690 - Built-in Grammar Checker Does Not Complain About "I can understanding English."
Summary: Built-in Grammar Checker Does Not Complain About "I can understanding English."
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 145855 (view as bug list)
Depends on:
Blocks: Proofreading
  Show dependency tree / graph
 
Reported: 2012-03-21 21:00 UTC by Ma Xiaojun
Modified: 2025-10-16 19:59 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
No Complain About "I can understanding English." (1.86 KB, image/png)
2012-03-21 21:00 UTC, Ma Xiaojun 		Details
Microsoft Word Does Complain (1.78 KB, image/png)
2012-03-21 21:04 UTC, Ma Xiaojun 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ma Xiaojun 2012-03-21 21:00:43 UTC 
Created attachment 58844 [details]
No Complain About "I can understanding English."

Type "I can understanding English." 
No blue wave line appear.

I prove the grammar checker is on by typing "I'm an boy." and see blue wave line under "an boy".

The attachment is screenshot of the issue.
Comment 1 Ma Xiaojun 2012-03-21 21:02:15 UTC 
By saying typing, I mean type in LibreOffice Writer.
Comment 2 Ma Xiaojun 2012-03-21 21:04:03 UTC 
Created attachment 58845 [details]
Microsoft Word Does Complain
Comment 3 Kumāra 2013-09-23 08:12:49 UTC 
XiaoJun, I'm happy to report to you that with the LanguageTool (www.languagetool.org) extension, you would get a blue wavy line for "understanding"! (In current inbuilt LightProof doesn't do much.)
Comment 4 Justin L 2025-10-16 19:14:31 UTC 
IIUC, lightproof is abandoned, so this bug report is basically dead. Use the WritingTool (formerly LanguageTool) extension instead.
Comment 5 Justin L 2025-10-16 19:59:07 UTC 
*** Bug 145855 has been marked as a duplicate of this bug. ***