AbiWord beats OpenOffice to a Grammar Checker
msevior writes "The recently released AbiWord-2.4 (downloads for Linux, OSX and Windows here ) is the first Free Word Processor to offer an integrated Grammar Checker. We can can do this because we're a pure GPL'd application and so can easily collaborate with other Freely licensed applications like link-grammar, gtkmathview and itex2mml which provide AbiWord-2.4 with a superb Latex-based Math feature.
Sun's license requirements for OpenOffice.Org make it much more difficult for such collaborations to occur."
Yay for F/OSS bloatware! (No offense to the poster)
Now if only they could have a floating thumb tack that gives you help whenever you don't need it.
Do people honestly use grammar check? Hasn't it been proven that no grammar checker works well enough to provide a wide cover of the English language?
Personally, when I write an article or something for wide dissemination, I'll send it to a group of writers I know and trust. Peer editing. They do the same when they need a human review. I'm sure there are websites to help others do similar swaps.
The MS Word g/c pisses me off bigtime. I have to disable it or go crazy.
For me, a grammar check is a bloat feature that doesn't add worth to a word processor. This is especially true for technical documents.
Is this a feature needed solely to promote the package (like the "often used" cruise control on every car) to the masses?
I'd rather have a thin distribution that works quickly without consuming massive amounts of RAM and processing power.
Am I alone?
[...] integrated Grammar Checker. We can can do this because [...]
:-)
I'm laughing at all you AbiWord and OpenOffice users from my tower of Notepad!
Even advanced grammar checkers still work very poorly compaired to sitting down, reading it yourself, and then having an english inclined friend do the same.
I suppose LaTeX support is nice for the math geeks, though you would think that they are already using a program with support for it if they need it.
From the Link Grammer link you provided:
http://bobo.link.cs.cmu.edu/link/
As of December 2004, we are releasing the parser under a new license; the license allows unrestricted use in commercial applications, and is also compatible with the GNU GPL (General Public License). You can view the license here. We are also releasing version 4.1b, which is identical to version 4.1 (released in 2000) except that the licensing statements reflect the new license.
Sun's license for OpenOffice is LGPL
http://www.openoffice.org/license.html
I'd be more concerned that if it were GPL'd that it couldn't use some or all of the above. Now arguably, OO does need to shed some pounds so if it dumped Python and / or Java that might be no bad thing, but that's a different topic altogether.
While theoretically correct, the practice is different: everyone is allowed to collaborate when the software has a BSD license. However, since it is not mandatory to publish the code, it really doesn't matter that much.
3 3 ]
...and therefore:
For example, the ASUS WL-500g (Linksys like router with USB port) its firmware is recompilable and hackable by you and me since it is (mainly) GPLed code. The newer SL1000/SL5000 (vpn routers) contain several BSD modules which ruin the party:
[From: http://website.wl500g.info/beta/firmware.php?fid=
Changelog:
SL1000 and SL500 GPL source code
Before using the source code, please note:
1. The router's firewall and VPN are licensed 3rd party code and are not subjected to GPL terms.
2. Several software modules are derived from BSD codes, which ASUS won't release.
[From: http://wl500g.info/showthread.php?t=3417 ]
There are no chance to build something useful from this sources.
...have a GOOD grammar checker?
The GPL discourages collaboration. If you want to encourage collaboration you need a license like BSD. The GPL allows restricted collaboration, but only between GPL fans. The BSD license allows collaboration for everyone.
If you are feeling altrustic, then BSD allows maximum freedom for your code. If you want the world to benefit from your code, but don't want someone ripping off your work and hiding it in a commercial project without paying you anything, then GPL gives you great protection. Even after you release something under the GPL you can still license it to a commercial closed-source enterprise for a fee, like MySQL. It only becomes a nuisance when the project grows and has many contributers as you then need to ask permission from each contributer before you can relicense. On the flip side BSD encourages more forking where the new code is not merged back into the main tree as there is no incentive. If the appropriate license is chosen then I don't think either will encourage collaboration more than the other as the license should reflect the goal of the project. A group writing printer drivers which their respective companies have agreed to make Open Source for pragmatic reasons may not want the same license as a loosely-knit group of graphics programmers wanting to release 3D modelling system. There are plenty of other licenses that can be used, though GPL, BSD and Apache licences currently have the greatest mind-share. There is no such thing as a best license, only the most appropriate one.
Phillip.
Property for sale in Nice, France
I'm a pro writer, so I live inside word processors. AbiWord is my tool of choice these daya on both Linux and Windows.
I turn off real-time grammar checking, because it distracts me from the act of writing. In my experience, grammar checkers are often incorrect in their analysis, particularly if you write fiction and technical works (as I do.) Unusual terminology and structure can give these checkers indigestion.
That isn't to say that I don't use grammar checkers. When I've completed a draft of an article, I often run the grammar checker manually to make certain I haven't missed anything obvious or silly. But I can't stand them in "real time", where I feel like I'm back in high school with the teacher looking over my shoulder and nit-picking every keystroke.
All about me
Actual uses of grammar check:
- As a partner to spell check, find correctly spelled but misplaced words (eg: there and their).
- Find common brain-farts such as reduplicated words.
- Remind blame-ducking idiots that the passive verb makes their evasions obvious. Mistakes were made, my foot!
- Point out incongruities and neologisms, which some people might not know aren't cultured english, such as excessive verbing of nouns.
These are all tasks that require an ability to parse grammar, and they're actually useful.To call them "grammar checking" would be too strong, but I can't think of a better descriptive name.
2.4 supports import of OpenDocument: from http://www.abiword.com/release-notes/2.4.0.phtml:
OpenDocument support
Support for the OpenDocument file format has been donated by INdT, Nokia's Technology Institute. Currently the OpenDocument import filter is basically complete, with support for styles, headers/footers, lists, image wrapping, text boxes, tables, footnotes/endnotes and tables of contents. OpenDocument export is planned as well and will be added during the 2.4.x series.
--
The world is divided in two categories:
those with a loaded gun and those who dig. You dig.
...any chance of integrating the grammar-checking code into Slashdot? Or would the code melt-down from an overload after being installed here for more than 5 minutes?
Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
The submitter praises GNOME's premier word processor in that it can surpass OpenOffice.org because it is GPL'ed, whereas the inflexible LGPL license of OpenOffice.org cripples development.
No, I think you (and most posters) misunderstand what the licensing issue is. The problem with OpenOffice.org is *not* that it's LGPL'd, but rather that for code to be integrated into OpenOffice.org, Sun requires you turn your copyright over to Sun. Very few existing Open Source projects are willing to do that--because frankly it's evil. This makes it very difficult for OpenOffice.org to integrate anything that isn't home grown.
The FSF also requires you to assign your copyright to them if you contribute to some of their projects (such as emacs -- I know; I've contributed to emacs). And you have to sign a document saying that your work is your own, and that you have the right to assign copyright to them (i.e. your employer has no claim over the code). This is to make sure that any code that goes in is legit, or at least that if they get sued for copying someone's code, they can point to the document and say that it wasn't their fault.
Of course, the free software community trusts the FSF a lot more than than they trust Sun.
To get something done, a committee should consist of no more than three persons, two of them absent.
An english grammar checker in OpenOffice will be useful when the english language acquires a good grammar. I don't see that happening for quite a while. In over 400 years of "modern english", it hasn't happened yet.
In fact, since the number of people who now speak english as a second language greatly exceeds the number of native english speakers, the diversity of acceptable english expression is increasing. English has always been very open to importing new sentence structures as well as vocabulary from other sources. English is a healthy growing language, that is changing almost from year to year as it absorbs and transmogrifies what these new english speakers bring to the party.
That's quite ugly, don't you think? Here is a TeX version to compare (kudos to Wikipedia's TeX renderer)
My other Beowulf cluster is... er...