Welcome to the home of OpenOffice.org extensions! 
LanguageToolby dnaber LanguageTool is an Open Source language checker for English, German, Polish, Dutch, and other languages. It is rule-based, which means it will find errors for which a rule is defined in its XML 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. It does not include spell checking. Note: Make sure the Java runtime environment 5.0 or later from Sun Microsystems is selected before you install this extension (see Tools -> Options -> Java in OpenOffice.org). Others versions of Java may fail to work. Source code: Browse source code License: opensource | Read license Further product information: Screenshots | Product details
|
||
Report abuse here
By any use of this Website, you agree to be bound by these Policies and Terms of Use
Sun, Sun Microsystems, the Sun logo, Java, Solaris, StarOffice are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
Comments
ObNewUser: LT failing to recognize page breaks and other breaks
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
documentation
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.
Removing the LT icon from the toolbar impossible
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?
not really possible
It's a limitation of OOo, as it seems. We'll remember about it in a future version.
Easier collaborative editing of rules
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.
second this suggestion
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
This is what we plan to do :)
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 :)
Not working for me in OS X
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.
The window can be hidden
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.
Issues Found
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!
New release solves most of these
Your points (except no 2, which I could not reproduce yet) have been addressed in the new release 0.9.2.
Progress on these issues
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.
could not create Java Implementation loader
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#jav...
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.
RE: could not create Java Implementation loader
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!
Exactly the same thing
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.
Try deleting java config
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).
Great!!
I like this extension.
It really works and it is really helpfull.
Thanks for this extension.
Dhruva
good start
This is a good start, but needs improvement. Thanks for the extension.
This extension is Awesome!!!!!
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.