LanguageTool

Maintainer:
dnaber
Rating:
3.875
Average: 3.9 (40 votes)
Application:
Writer
Tags:
grammar, linguistics, grammar checker, proofreading, style checker
Screenshots:
http://www.languagetool.org/screenshots/
Source code:
https://github.com/languagetool-org/languagetool
Post date:
Friday, 7 September, 2007 - 15:51
Statistics
Week: Not tracked - Month: Not tracked - Year: Not tracked - Timeline
Download extension
System Independent version - All releases
Compatible with OpenOffice 4: Yes
User feedback:
Compatible with OpenOffice 4.x?

LanguageTool is an Open Source language checker for English, French, German, and other languages. It is rule-based, which means it will find errors for which a rule is defined in its configuration files. Rules for more complicated errors can be written in Java. You can think of LanguageTool as a tool to detect errors that a simple spell checker cannot detect, e.g. mixing up there/their, no/now etc.

It can also detect some grammar mistakes. When used in OpenOffice, it does not include spell checking.

Important: in case of problems, please read the checklist page on our homepage

Supported languages: Asturian, Belarusian, Breton, Catalan, Chinese, Danish, Dutch, English, Esperanto, French, Galician, German, Greek, Icelandic, Italian, Japanese, Khmer, Lithuanian, Malayalam, Polish, Portuguese,Romanian, Russian,Slovak, Slovenian, Spanish, Swedish, Tagalog, Ukrainian . Please note that the level of support differs a lot between languages.

LanguageTool

Version Operating system Compatibility Release date
2.5 System Independent 3.4, 4.0 31/03/2014 - 08:11 More information Download
2.4 System Independent 3.4, 4.0 30/12/2013 - 09:54 More information Download
2.3 System Independent 3.4, 4.0 30/09/2013 - 13:19 More information Download
2.2.0 System Independent 3.4, 4.0 01/08/2013 - 15:57 More information Download
2.2 System Independent -- 30/06/2013 - 15:48 More information Download
2.1 System Independent -- 01/04/2013 - 16:08 More information Download
2.0 System Independent -- 30/12/2012 - 11:47 More information Download
1.9.0 System Independent -- 30/09/2012 - 18:36 More information Download
1.8 System Independent -- 30/06/2012 - 18:19 More information Download
1.7 System Independent -- 25/03/2012 - 15:58 More information Download
1.6 System Independent -- 16/03/2012 - 14:19 More information Download
1.5 System Independent -- 25/09/2011 - 10:48 More information Download
1.4 System Independent -- 26/06/2011 - 18:03 More information Download
1.3.1 System Independent -- 29/03/2011 - 16:25 More information Download
1.3 System Independent -- 27/03/2011 - 13:45 More information Download
1.2 System Independent -- 02/01/2011 - 11:20 More information Download
1.1 System Independent -- 26/09/2010 - 11:10 More information Download
1.0.0 System Independent -- 01/11/2009 - 14:09 More information Download
0.9.9 System Independent -- 22/05/2009 - 15:07 More information Download
0.9.8 System Independent -- 26/04/2009 - 07:51 More information Download
0.9.7 System Independent -- 03/03/2009 - 17:19 More information Download
0.9.6 System Independent -- 21/01/2009 - 18:06 More information Download
0.9.5 System Independent -- 02/11/2008 - 14:45 More information Download
0.9.4 System Independent -- 30/09/2008 - 17:05 More information Download
0.9.3 System Independent -- 07/08/2008 - 16:35 More information Download
0.9.2 System Independent -- 17/02/2008 - 16:50 More information Download
0.9.1 System Independent -- 25/09/2007 - 03:11 More information Download

Comments

This is a good start, but needs improvement. Thanks for the extension.

Can't see how this extension has such a low rating. I think for the majority of users it is as good as it needs to be. Sure, sometimes it might pick up things that are not actually a problem, but when this is the case you can just ignore the advice. Thanks to everyone who has developed this. It has added a lot to open office.

I like this extension.
It really works and it is really helpfull.
Thanks for this extension.

Dhruva

Hi, I am getting this error (above) when I try to install or enable the extension. I see the error is referenced here:
http://wiki.services.openoffice.org/wiki/Extensions_trouble_shooting#java_loader
but the page isn't clear about what an end-user should to resolve the problem.... It suggests "This usually happens when one wants to debug Java in the office process and therefore has provided the debug options for Java in the options dialog. ' However, I have checked my Java settings in Open office, and I don't have any debug options entered.

Exactly the same thing happening here, running OO 2.3.1 British English on Gentoo Linux, with two JVM installed (1.5 and 1.6), both fail.

In your home directory, there should be a configuration dir for OOo (called oo2 or openoffice2 or whatever). Go there, find config directory, and rename java*.xml to java*.xml.bak. This worked for me yesterday in Suse - seems that OOo couldn't save the option I tried to save (though the permissions were set correctly).

Try Tools...Options...OpenOffice.org...Java, tick Use a JRE and select a different (newest Sun?) one.

I have Sun Microsystems Inc v 1.6.0_03 which I installed and Free Software Foundation 1.5.0 (gcj-java version installed as default with Fedora 8). Mine was set to the FSF version and I got the error, but it worked when I enabled the Sun version and restarted OpenOffice.org. I had already used /usr/sbin/alternatives --config java to set the Sun version as system default but OpenOffice.org seems not to have picked that up (or perhaps it was over-written on an upgrade, I'm on 2.3.0-6.6.fc8).

Good luck!

I reviewed this plugin for citywide (City of Largo) use, and found the following issues that prohibit use:

1) It does not seem to understand global multi-user installs. If you install from root it it pushed to all users, however when you try and customize your own settings it's trying to write into the global settings area and fails. Settings should go into $HOME

2) The [ Close ] button fails to close the UI and requires the "X" of the window manager

3) The "LT" floating toolbar on initial install is going to cause problems with most of the users. It should be docked on first use.

4) LanguageTool should be moved under Tools >> and not be it's own menu option. This breakage of standards will be difficult to train people.

This is a good start for sure. The main logic seems to be working well and will be helpful to us.
Thanks!

Issues 3 and 4 have been addressed in the development version. I cannot reproduce issue 2, could you please contact me via email about that and send me more details, e.g. if there's output on the console if you click the button but nothing happens? I yet have to think about issue 1.

In 3.0.1, we switch to native dialog in OOo, so the issue [2] will not be present. Also, issue [1] has been fixed by using user home directories for storing preferences.

Your points (except no 2, which I could not reproduce yet) have been addressed in the new release 0.9.2.

Just tried this out with the development version of OOo Aqua for OS X and I'm having problems. It installs fine. Other than in the extension's manager, the only sign that LT's been installed is a button on the toolbar. Clicking this button does nothing. No window appears. Since this is a development version of OOo, I'm not sure if it's an issue with OOo or with this plugin on OS X. According to the Java preferences, J2SE 5.0 is being used (full version is 1.5.0_13-b05-237). Thought I'd let you know. If you'd like someone to beta test for OS X, I'd be happy to help, though I'm not sure where to start debugging.

This could be a known bug in OOo: the LT window can be opened in the background and actually sit behind the main OOo window. We can't do anything about it, it's just OOo misbehaving...

If you don't see any window in the background, simply try to start OOo from the command line and see what messages appear when you click the button.

It may be good if users could improve the rules for the whole project, for example using a web form. After the user updates his/her local rules, the extension would suggest adding the modifications to the experimental rule base. Users also have the option to receive updates to the experimental rule base. The history of changes should be tracked and there should be a place to discuss changes (maybe like a wiki). Then the rules from the experimental set can be periodically added to the official rule base.

I've only recently began using OpenOffice and finding this grammar tool was a godsend. I do a great deal of writing, both recreational and professional, and when I was using Word I relied heavily on the grammar checker to confirm my syntyax.

As a programmer I also know how difficult it is to cover every rule. Pgan has a good suggestion. Users can add words to dictionaries, after comfirming the spelling with a reference dictionary. Being able to add grammar rules would be helpful to not only the programmer but also the users.

As a writer, I've noticed a few things in the current version that need addressing.
1. When I am quoting text from another source it marks the quotation marks as unmatched - possibly because of a line break in the quote since it only seems to catch those. When "quoting" there may be line breaks and the rule should consider that if it's possible.
2. When I use the word "too" as in 'there is too much junk in here' it flags the use of "too" and wants it changed to "to". I'm not quite sure how to correct this rule as I don't know the syntax for the rule.

Which brings me to my question. Is there a way that those of us who are proficient in grammar can help with constructing the rules and testing them. I've taught basic grammar online to other writers and would be happy to help. My programming background would also be a plus as I can read code and understand it, whereas a non-programmer may not be to understand the coding. I don't know Python, but I've done a bit of research and the syntax is familiar.

If there were a way to help I would be happy to assist. Just let me know. ~grins~ And... I'm good at finding bugs and reconstructing them for study or correction. Also, I can often tell why something is acting the way it is - as demonstrated by my comment on quotation marks.

In closing, thanks for the wonderful tool. It has a lot of potentional.
Dreamer

Have a look on our new website:

http://community.languagetool.org/

This should address most problems you mention. We'll be adding more features (like rule editing online) in the future but you can test rules on your own input or Wikipedia now.

BTW, the rule that raised a false alarm for "too much junk in here" has been already corrected in current development version :)

Does anyone else have the problem, that removing the icon from the toolbar is impossible?
I only want to have the menu entries to access the functionality.
I tried to remove the icon by unchecking the checkbox in the toolbar menu, but it wont uncheck on click.
When using the toolbar manager, the LT entry does not show there.

Any fix on that?

It's a limitation of OOo, as it seems. We'll remember about it in a future version.

I just ran it on a test document that I knew had affect-effect errors and it didn't pick up any of them. I would be willing to attempt building a new rule but can find no documentation on how to build rules.

it also seems to spawn another instance of OO.o on the Mac Dock which if closed, results in the closure of both instances. Rather confusing behavior.

Quite a few of the flagged errors in the Wikipedia tests at the beta website, , are failures to distinguish headings from full text.

I also had an incorrectly flagged capitalization error when a sentence spanned a page break in a OO.o-Writer document (in MS-Word format). I am wondering if there is a more general failure to detect various sorts of 'breaks"?

I am interested in contributing to the project but the website gives no links that support such interest.

--
David

Rule development is described at
http://www.languagetool.org/development/

Several OOo integration bugs should be solved with the new OOo 3.0 which comes with a grammar checker API that LanguageTool is going to use.

Unfortunately in my system (Windows XP SP3, OOo 3 rc1) LanguageTool 0.93 makes Writer unstable. It crashes or hangs suddenly.

See: http://www.openoffice.org/issues/show_bug.cgi?id=93883

Crash is fixed in OOo 3.0 RC3 and in 0.9.4 release of LT.

The requested URL /download/LanguageTool-0.9.3.oxt was not found on this server.

Thanks, the link should be fixed now. We renamed to file to alert users about a bug in even the latest beta version and release candidates of OOo that makes this version of LanguageTool unstable. We cannot do anything about this and have to wait for the final release of OOo 3.0.

We have LT in production on OOo 2.4 and it was working well. I had to pull it from our 3.0 install because it's causing OOo to crash on lots of documents.

Here is one of them:

http://www.openoffice.org/issues/show_bug.cgi?id=94855

The crashes for this document were fixed in the CVS - there was an error in one rule for English that detected multiple whitespace characters. Now it should work fine - if tests run fine, 0.9.5 will be available soon.

I have received the upgrade and so far so good. Your quick response is appreciated!
-thanks

When I put my footnote anchor at the end of a sentence after the period it tells me that the Capitalization of the new sentence is wrong. Could you correct it?

OO 2.3.1, LT 0.9.2, Java 1.6.7

Sorry put comment in wrong place. . .

I can't get this Language extension to work. The button is there, as well as the Tools/LanguageTool drop-down menu. I used a sample sentence from the screen shot. But no errors are highlighted. Tried several other obvious mistakes with the same result.

The extension installation went okay. Tested Java and it's working fine. I'm running Vista, SP1. Have Java 6 update 7 installed and enabled in OO. Running OpenOffice 3.0.0; OOO3000m9 (Build: 9358). Followed instructions precisely. Restarted OO before trying to use this extension.

It just doesn't work for me!

What could be wrong?

The install info said to restart Open Office after installing this extension, which I did; however, nothing was said about rebooting the OS. (Apologies, if I WAS supposed to reboot--couldn't find anything about that.) Anyway, it finally occurred to me to try a reboot, and it worked! Now the grammar tool is working well. :-) Looking forward to using it. Thanks!!!

OpenOffice.org QuickStarter loads with your OS, and you need to disable it (as we mention in the install instructions). Rebooting also disables it, so you can do this via rebooting as well.

I use it with German but some times I write Greek too. When the "check grammar" option in the spell check dialog is activated I have two problems.
1)With German Text. The dialog does not work and does not spell check but it doesn't crash. When I remove the the "check grammar" option the spell check dialog works fine.
2) When I write Greek and the "check grammar" option is activated OO crashes. No reaction.
It means that I have to start spell check a German file and then I have to deactivate the "check grammar" option. After that I can spell check Greek text too.
I have the crashes only with the spell check dialog. When spell check as you type is activated there are not crashes when I correct with right mouse click.

OK I know it does not support Greek but I should be able to deactivate it without a crash.

My opinion is, that it is a very good extension and it is usable with the German language but it needs some additional work.

OO 3.0 Win XP HOME SP3 LT 0.9.5

Please disable "grammar check" checkbox in the spell-checking dialog. The dialog is buggy and it will be fixed in OOo 3.0.1 (it's not LanguageTool code, it's OpenOffice.org).

The only way to use LT in OOo is via our menu or with automatic checking - then nothing crashes. :)

Is there a work around.?
Regards George

Which version did you try? Only 0.9.2 can work with OpenOffice.org 2.4.

Hi. I installed LanguageTool 0.9.5 in OO 3.0 under Windows and Java 1.6.0_10.
I noticed that there seems to be no way to mark a supposed problem as ok. Furthermore the extension seemed to slow down OO Writer.
Therefore I removed the extension. However, the error marks (blue wriggles) still kept reappearing.
To get rid of the extension, I had to deinstall and reinstall OO.
As long as there is no clean uninstall, I would advise against using the extension (at least in mentioned configuration).

Deinstallation of extensions is the responsibility of OpenOffice.org, so if you can reproduce this (I can't), please open a bug report at OOo. As usual, you have to quit OpenOffice.org and the quickstarter after installation and deinstallation of (some) extensions.

The LanguageTool error marks still showed even after reboot.

The bug is not reproducible here as well. Do you remember if LT remained in the Extension Manager after deinstall?

Is your username with spaces or special characters? In such a case, OOo has a bug with Java extension installation...

LanguageTool was not shown in the extension manager after deinstallation. However, it was still active and marked errors.

Even after reboot? Deinstallation of the extension must be followed by closing OOo to desactivate LT completely (though OOo doesn't tell you that). You must also close the QuickStarter, if it's open.

The ability to ignore errors is in our configuration dialog. Simply open it and find the rule to disable.

Note: the dialog and grammar checking menus in OpenOffice.org are still a little buggy. Wait until 3.0.1 release to see. The changes introduced in 3.0.1 solve the issue with ignoring errors.

LanguageTool at present does not allow the user to ignore a supposed error for once and for all, e.g. if the error is no error. Or am I mistaken? Therefore I would like to have the tool inactive most of the time, because the error marks are obnoxious. Once in I while, I would use the tool to check the text (and would have to process the erroneous errors again and again). The configuration dialog allows disabling certain rules (or all). But the configuration should not be affected by making the tool inactive.

This is not LanguageTool that does not allow to ignore the error once and for all, this is OpenOffice.org 3.0.0. However, with 3.0.1 it works fine, and the ignored rules are remembered. So please wait until 0.9.6. Also, the quality of the English checker has been improved (less false alarms).

Could you please elaborate what you mean by saying "But the configuration should not be affected by making the tool inactive." I don't quite get it.

Hello,
Since I started Language Tool for the first time, Writer crash at start-up when I open a document from the Explorer or when I am trying to use Language Tool inside Writer. There is a long list of messages starting by:
Java.lang.RuntimeException: Failed to load rules: Loading rules failed: Duplicate Class definition:
......CommaWhitespaceRule, found in C:\.... \LanguageTool.uno.jar

I am using XP Pro Sp3, Open Office 3.0.0 build 9358, and Language Tool 0.9.5
Anything I can do?

Thanks
Gautier

Does your username in Windows contain only pure ASCII characters? If not, then strange things might happen because of the bug in OpenOffice.org. Try installing for all users as admin and see if it works that way. Please also remove LT from OOo before you install it for all users as admin.

The OOo bug has been already fixed but will be visible in 3.2, and not in 3.0.1.

Update from 0.9.5 to 0.9.6 failed. Extension manager reported a long list of Java failures, and now I can't remove the old version (0.9.5) which is not working. The old one is not working, you can't remove it or to update it. Think twice before installing this one.
I have OOo 3.0.1 (OOO300m15, build 9379) on Windows XP.

JusSi

You cannot "update" directly from 0.9.5 to 0.9.6. You need to remove 0.9.5 in OOo 3.0.0, then update to OOo 3.0.1, then install LanguageTool 0.9.6.

Why is that so? I just updated Googledocs extension from 1.41 to 1.4.2 and the extension tool just told me that it will replace the older version. If this is not possible in the case of Language Tool, then it should be explained very clearly in the website.

I had already 3.0.1 when I started to update - and now I had to remove whole OOo and reinstall it again to make an extension functional. Makes no sense for me. Sorry.

JusSi