Maybe I'm not understanding, but why go back all the way to Abiword 1.0.7? I would just use Abiword 2.2.9, which came with Slackware 10.2 and runs fine without Gnome.

Ah thx that sorts the font problem out, but that package must have been built with the wrong --prefix or more likely left empty.

It does require some gnome libs though:

abiword: Requirements: enchant, libgnomeprint, libgnomeprintui, libgnomecanvas

Sorry, I uploaded a testing package. Please find the correct one under the same link:
http://distro.ibiblio.org/pub/linux/...0.7-i486-1.tgz

Perhaps I'm missing the big picture here. Seems the OP wants to continue using Abiword, but is concerned that Abiword will not be supported in future versions of Slackware.

Seems to me that the OP is not looking for a text editor but wants to use a word processor. A word processor provides additional formatting tools typically not included in text editors. The OP should be able to continue using Abiword and replacing Abiword with text editors is not a preferred solution.

The OP has implied that using a typesetting program such as Latex is not a preferred solution. The OP also does not want to install KDE to use KOffice and does not want to install a complete office suite such as OOo.

If the OP currently is using Abiword, then all associated GTK library files must already be installed. However, Abiword apparently requires a nominal few GNOME libraries. Those library packages also are already installed on the OP's box. The challenge then is how can the OP continue using Abiword with subsequent Slackware releases when there will be no Abiword package provided?

One solution would be to continue using Abiword as is with the currently installed version. That might or might not be a viable solution. On my Windows box I have been using Word 97 for 9 years, and there is not a single feature that is included in subsequent versions of Word that motivates me to update from Word 97. In Windows, Word 97 fits all of my existing word processor needs and I see no reason to update that package. Possibly the OP can view the current version of Abiword in the same manner. If so, then updating Abiword might be a moot point. Simply update Slackware as needed but leave the current Abiword installation alone.

The probable challenge, however, is updating to future versions of Abiword should the OP discover new features or bug fixes that the OP seeks.

The challenge then for the OP is merely finding an installable Abiword package. As is true with many computer users, the OP does not seem inclined or motivated to compile from source. However, my guess is that somebody at www.linuxpackages.net will provide such a package if asked politely at the linuxpackages forum. I am more than willing to believe that the OP is not the only Slacker who will be affected by PV's decision to drop Abiword and that somebody at linuxpackages will post an Abiword package for Slackware. My recommendation then is for the OP to post a query at the linuxpackages forum.

Okay, I'm too stubborn to just let it go. If you read the BUILD.TXT file in the abiword-2.2.9 source, it says that AbiWord will only use the enchant library if it finds it. I'm not gonna dig through the rest of the files just to prove a point, but here's an excerpt from the Slackware Changelog...

=====
Thu Feb 16 14:01:26 CST 2006
OK, I think I have everything that used libreadline.so.4 recompiled with the exception of AbiWord, as the --disable-gnome option no longer seems to work with abiword-2.4.2 -- it still demands libgnomeprint and all of its dependencies. Anyone know a way around this one? If not, AbiWord will likely be removed soon. It's included in all of the GNOME distributions for Slackware anyway.
=====

In other words, it's silly to go all the way back to Abiword 1.0.7... unless there's some other reason you want to do that. Just use abiword-2.2.9 from the Slackware 10.2 release.

I stand corrected then. It's a pity about the lack of the --disable-gnome option in the latest version.

Maybe google around for flwriter used by DSL and other really light distros. I doubt if it'll open MS .doc files, but maybe ... and, if not, it'd probably be a good project.

I offer the old version as being the best available for use on systems without any Gnome, Glade or even GTK-2.x. Version 1-0.7 only needs GTK-1.2, gdk-pixbuf and libxml to compile.

If the OP has GTK-2, the best might be to stick by the last version that would work without gnome and recompile from source when needed for forward compatibility. I mean if he can live without the latest bug-fixes (or bug-introductions).

For people who want an even lighter word processor, there is 'siag' which also includes a tiny spreadsheet. It uses athena widgets.
'ted' is a pretty good with .doc and .rtf.

I remember seeing the note in the changelog and have thought putting myself to the task. I maintain some packages that use GNOME-1.4 and GTK-2.x, but spend most of my time adding to my GTK-1.2 collection.
I cringe when I have to install GTK-2! I actually like GTK2 very well, but I work on a 333Mhz PII. And I mean lots of work! KDE and GNOME are obviously out. Even XFCE4 is heavy. I use my own AFX-ROX-Filer for GTK-1.2 on IceWM or WindowMaker usually. Don't do this on faster machines -skid marks you know? :-)

ROFL. I have a laptop with a Celeron 1.8 Ghz processor, and I'm using WindowMaker with mostly GTK apps. Another thread here reminded me of Midnight Commander and I've been using that again lately. You DO have to be a little careful around corners or you end up on just 2 wheels. I tried WindowMaker on an AMD64, but it was just too dangerous.

I came around "Antiword" when checking the ports on bsd, i have no idea if it may help or if even related to post, maybe worth checking, here's link anyway: http://www.winfield.demon.nl/index.html

LOL

A humorous typo, of course. At 700MB that would make Joe's Editor the Sumo wrestler of text editors.

Dennisk

well u can always keep your existing slackware and not upgrade. just keep your kernel and other packages up2date. use the abiword u use now.

I have AbiWord-2.4.4 running without Gnome! But it's a gross hack. Let me back up...

I spent about 10 hours yestderday on this problem, studying and compiling vesrions from 2.2.9 to 2.4.4. The upshot is this:

1. The last version which will configure and compile without gnomeprint (using --disable-gnome --disable-enchant) is 2.2.11. You need fribidi and of course pango and libxml2.

2. Version 2.3.0 introduces dependency on libgsf, which is not required for 2.2 nor 2.4 versions. Version 2.3 breaks without gnomeprint because the print preview routines are changed. By changing configure and makefiles you can get later versions to succesfully configure and get through most of the compile -up till the print preview routines. By using the files from 2.2.11 over the current ones, you can make this compile and run.

3. Version 2.4.4 and 2.4.2 both have another gnomeprint problem. A routine for handling PDF files also depends on gnomeprint. Changing the makefiles will get you around this also. However, I don't know what effect this has on functionality. New files are added for this routine, but I haven't discovered if it's a new feature or just rearranged code.

2.4.4 when compiled this way will run, but it segfaults if you choose Print Preview from the menu. When I compile 2.2.9 it shows no menu entry for Print Preview, which seems right if it's only available with gnomeprint libs. A small fix will remove the menu entry -when I find it.

Does the 2.2.9 which you use provide Print Preview?

I think I can hack 2.4.4 to work this way, but it would definitely be a hack, removing newer features and such. A better solution would be to have gnomelibs and gnomeprint available on your system for compatibility. I've produced a mini GNOME-compat package for GNOME-1.4 before. I've thought about doing this for GNOME2 as well, since it's not included in Slack anymore. I have no interest in maintaing packages for a full GNOME installation, but there are *lots* of programs that need some of the libs.

I'm willing to do some more work on this. But I'd rather package the libs than get serious about hacking another program. Another idea -I could maybe compile the gnomeprintlibs statically into the binary for 2.4.4.
What do you guys think?

A very interesting thread.

It seems the OP would like a Linux WP which Nisus fills in the Mac world. Small, fast, stand alone with enough features to get writing and not worry about "the other stuff."

Currently we don't seem to have that under Linux, as the alternatives mentioned here do not seem to fit the bill for one reason or another.

I'm with Randux...

Until Nisus produce a Linux version, I'll stick with OOO which does a great job.

Regards,

dkpw