Languagetool Needs Your Help

We need your help! No matter if you're a Java developer, translator, proof-editor, linguistics student, or just a volunteer, you can help make LanguageTool a better checker.

• Language maintainers help develop rule files for new and existing languages. They do not need any special programming skills. All that is required is some basic understanding of grammar and ability to use a formal notation.
• Language testers help review false positives using the community website. No special skills required; you just need to be fluent in your language.
• Swing developers can help us make better UI. Currently, the configuration dialog is too cramped and at the same time lacks several elements. The fix is simple but we have other priorities.
• OpenOffice.org help maintainers can help us create special help pages for LanguageTool, possibly also with more detailed descriptions of the rules.
• Translators can help us fix the SRX segmentation file just by using it in their favorite CAT systems and reporting back weird segmentation.
• Proof-editors can help us by sending sentences in which LanguageTool didn't detect any problems but which are definitely incorrect. The more frequent the error, the more interesting it is.
• Linguistics students can help us support new languages or add new rules (sometimes it's enough to suggest an idea of a rule - just a sentence with an error and a fix).
• MacOS owners can help us by regularly testing the releases. Java on Mac works differently on different versions of OSX. We need more testing in this area.
• GNU Java developers can help us make LanguageTool work for GNU Java. We don't know what's wrong with our way of using GetResource().
• Firefox extension developers can help us make a Firefox extension (there are some examples and we want to make it work similarly to the way SpellBound worked)

Simply contact us via our mailing list and we will surely use your help! Thanks! :)