KWord
 

I hope the next build renders html pages with their original formatting rather than just presenting the raw code.

No question in your post, so this thread has been moved to the General Forum.

Okay.

Anyway, I quite like Kword. The whole frames thing is a bit off the beaten path for someone who's been used (so far) to MSWord and OOWriter, but once you get the hang of it it's kind of fun to be able to paste pictures, tables, graphs, etc into a document and play around with the positioning. It'd make a great WYSIWYG web page editor (I currently use Iceape Composer for that, but it has nowhere near as much flexibility so far as placing things goes) IF it was able to import and export html files a lot better.

Of course, if I had the first clue how to use CSS maybe I wouldn't find Composer's table based approach so restrictive.

Not really sure what your question is, but CSS is not that hard to learn.

Here is the book that got me "over the hump":
http://www.amazon.com/Spring-Into-HT.../dp/0131855867

More at the author's website:
http://molly.com/books.php

Bah, books for CSS are useless when you could just as easily find a site, take their CSS file, and look at it, dissect it within Composer or something like Gedit/Kate.

Oh, and I like KWord too. I don't think HTML rendering is a high-priority, general functionality of a word processor comes first :)

KWord's not bad, but I do opine that OpenOffice leaves it in the dust.

I'm not here to start a flame-war. If you have a job to do, the first step is to find the best available tool for the job. Since discovering OpenOffice, I haven't given KWord much time-of-day.

I mean this as a slam to no one: least of all the KWord developers!

i occasionally use Kword when im writing small stuff that i dont want the time and ram expense to fire up open office.

open office is great but its bloated as hell!

And "BAH" to you too....;)
The book I cited was not useless---what you describe CAN be a good way of learning if you already sort of know something.

Everyone learns differently, but actually trying things is a common denominator--that book excels at getting you to do simple things so you see how it all works.

Ahh, there's tons of sites out there for CSS work. I really don't think there's a point to using books to learn these sort of things...

But your mileage will vary. People learn different ways.

By the way, OO.o isn't bloated. It uses the allocated memory in a quite unique way; it uses 128MiB 99% of the time. Try opening tons of files in OO.o, and I'll bet you RAM usage won't climb much higher. MS Office, GNOME Office, KOffice, etc. all start small but later mushroom in size. Good for quick edits, yes, but when you've got the app running 24/7, go for OO.o.

Especially if you've got the 64-bit "server" Java compiler. Open and let OO.o run for a while (10-15 minutes?) come back, and it should get pretty darn fast after a while.