AbiWord 2.2 Unleashed
uwog writes "AbiWord 2.2 marks a new milestone in the life of our beloved Ant. With a native port to MacOSX, and new features such as live updating tables of contents and TextBox support, Abi is finally a grown up Ant. Read the full announcement or go grab your own copy."
The appeal of Office suites is that you can create a document of some kind in one, and import data from another component. With OpenOffice, KOffice and Microsoft Office you have a pretty robust toolset for creating documents with mixed data. Where is AbiWord going to go along these lines? Are we going to see "AbiExcel?"
I seem to remember that in the beginning, the group was going to put out an entire office suite, but then got bogged down just trying to create the word processing component. A small and dedicated userbase, aside does Abiword have a future without these other components?
Click here or a puppy gets stomped!
now that we have OpenOffice?
Also, aren't word processors kind of backwards compared to typesetting systems?
Finally, a word processor that works on Macintosh, Windows and Linux.
No Openoffice on Xfree86 does not count
That's a shame as I might have looked at it as an alternative to OOo which is having a problem with numbering in a template I need to use, but the document has a lot of images in (OOo also has issues with the images). Mind you, even MS Office has problems with the numbering in a template and its numbering generation tools seem to have serious bugs anyway. I suspect the problem lies with the MS format somewhere.
I don't really care if they talk to eachother or understand their respective formats. I suspect that the vast majority of users out there probably feel the same way.
Wrong. Integration is absolutely essential for an Office suite. Every single document I create (mostly technical reports) have some sort of embedded graph or table.
Without that feature, the word processor is useless for me.
... is that OO is a complete suit, but the word processor part isnt as MSWord compliant as Abiword. Abiword is more MSWord compatible, and is standalone. They both startup slow and take more memory than good quality opensource software should.
When OO was new, I thought it was the Abiword killer.
I also dont quite get why Abiword isnt packaged as a part of OO. License incompatibility?
Lastly, I'm waiting for the firefox of word processors, something sleek and lean, fast, stable, with only the functionality I need, yet compliant with MS Word 2000. I've only needed Word and Excel, and these two applications need not be in the same office suite; only fast and compliant.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Attention, everyone. This guy logged a bug and it got actually fixed in the next version. That's a lot better than OOo's trackrecord (I've logged a bug which is heading towards two years and not fixed). This really says something about the development team, enthousiastic and not bogged down by crazy procedures.
I've just compared soffice and Abiword for win32 on "War And Peace" from Project Gutenberg.
soffice takes about 50 Megs of memory, and free()s most of it when minimized. A nice feature, imo.
Abiword on the other hand takes about 164 Megs, and constantly burns a few cycles for whatever, I don't know what. It also doesn't free() memory when minimized. So, for that huge documents (~1300 pages) soffice seems to be a lot better, at least technically. AbiWords UI feels more intuitive though.
Truth arises more readily from error than from confusion. -Francis Bacon
The older vesion 2.0.6 could not handle Urdu (Nafees web) fonts. Abi could display individual characters, but could not join them. I have not checked this version. The KDE apps do handle these fonts well, whereas Gnome apps fail (firefox even with pango enabled). Interestingly, Gaim does a much better job, but has a problem with a few characters. For Urdu, KDE is the way to go.
I wonder just how hard AbiWord will get hit when OOo 2.0 comes out this year. You know, an OOo that doesn't take half of the morning to start up...
Hey, congrats on getting post #11000000 it only seems like yesterday that we had the 10 millionths