Word Processors, Linux, and Writing
I use Linux and as a writer, this is a problem. I like using Linux because it’s stable. It never crashes, I never have to worry about viruses or spyware, and I can control what ads I see. In my normal Internet browsing, I see maybe two ads every hour or so, compared to a constant barrage of ads on Windows. Using Linux is much more peaceful.
But there are problems with Linux, and one of them is the word processor issue. Most editors use Macs or Windows, so documents need to be in .doc or .rtf format for them to access my work. Most people who use Linux recommend OpenOffice, which I tried out when I first switched over from Windows. I hated it. It is the most annoying program ever. It has all these strange defaults, like finishing words for you when you start to type them, that forces you to rifle through the options and turn off the annoying stuff. It also has trouble reading .docs and wants everything to be in its proprietary .odt format. Even if you change it over to .doc, you can’t be sure it stays that way. I have sent editors documents in .doc and found out that it switched over to .odt somewhere along the way, and the editor couldn’t read it. This is embarrassing and annoying. So I don’t trust OpenOffice and don’t use it.
For awhile I used AbiWord, which is a simple and stripped down word processor. I like AbiWord as a program, but it doesn’t have some basic things you need as a writer. It also uses the proprietary .abw format, which I found to have all the problems of OpenOffice plus the added issue that no one uses AbiWord, so it can be downright impossible to access your .abw file under certain circumstances. I recall having a terrible time accessing a .abw file from a Windows machine, since Windows doesn’t have anything remotely able to open it. Worse, Windows couldn’t even read the name of the AbiWord files, so they came up as gobbledygook. In short, I need something more sophisticated than AbiWord.
Finally, I settled on CrossOver Office by CodeWeavers. It lets you use Word on Linux. I really like Word. I think it is a good program with minimal problems and I am happy someone figured out how I could use it on Linux. But CrossOver Office has problems too. For example, you can’t open two Word docs at once without it getting buggy and crashing. I have lost a lot of work this way. There have also been problems with it deciding to paste something many many times. I would copy something from a website, hit CTRL-V to paste, and then everything freezes while it copies the text 300 times into my document.
So there are lots of bugs that I have learned to anticipate. Over time, I have developed a hybrid system of Word and OpenOffice so that my work is more stable. If I have to have two documents open, I open one in OpenOffice, which keeps Word from crashing. If I see signs that Word is getting unstable by freezing or using a lot of CPU, I reboot the computer. Etc. Overall, it’s not too bad of a problem, but losing part of an article while on deadline is not fun.
This morning I read that Susan Orlean is abandoning Word to write her next book on Google Docs. I don’t use Google Docs and definitely would not write a book on it. The problem is that their Terms of Service claims rights over your work. To quote from the Terms of Service itself:
You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Service. By submitting, posting or displaying the Content you give Google a worldwide, royalty-free, and non-exclusive license to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content which you submit, post or display on or through the Service for the sole purpose of enabling Google to provide you with the Service.
So it looks like Google is saying it can reproduce or publish any portion of your work that you put on Google Docs! I’m no lawyer, but that’s enough of a red flag to keep me from ever using it. Plus, that’s just a creepy policy, Google. What the heck?
On top of that, according to my computer-expert husband, putting your book on Google Docs poses a security threat, especially if you are a big-time writer like Susan Orlean. Here is part of our IM conversation about it:
(09:14:56 AM) Kyle: what it really comes down to is whether google would ever actually try to do that [publish your work]
(09:15:05 AM) Joy: yeah
(09:15:10 AM) Kyle: and if they did, it may not matter what their terms of use say, you could still sue them
(09:15:35 AM) Kyle: but what it also means is that if they have some security problem (like, say, Facebook has been having) someone could grab a pre-release book from an author and publish it
(09:16:41 AM) Joy: oooh!!!
(09:17:08 AM) Kyle: even if their security is somewhat sound, it doesn’t mean an author’s google password is
(09:17:31 AM) Kyle: and if someone knows your password for google calendar or gmail account (or can hack into it), then they can get into google docs
[Short amount of time passes]
(09:21:54 AM) Kyle: heh this is fitting, gmail had a 4 hour blackour earlier today
(09:22:07 AM) Kyle: imagine if you were on deadline and google docs had an outage
(09:23:45 AM) Joy: wow yeah. that would be horrible.
So there you go. OpenOffice? Out. AbiWord? Out. CrossOver Office: Usable, but buggy. Google Docs: Super-duper out! What’s a Linux lover to do?












