Word processing on OS X: my personal choices

A colleague asked me about what I use for word processing on the Mac. I started to respond, then realized it could be a quick post.

Briefly, I use Nisus Writer Express (NWE). It uses .RTF or .DOC as its native file format; that one absolute requirement of mine wiped out all the alternatives except Microsoft Word -- and I don't like Word. NWE is Cocoa native and works well with OS X services, it does the basics well. It has a great UI and has been fast and reliable in my experience. My wife uses it without any problems.

I haven't written any very long documents with it however.

Nisus has recently released Pro version of NWE. I'll eventually upgrade to, but it's a low priority for me. If the Pro version had a true outliner I'd probably have done it by now.

Nisus does a fair job importing simple Word documents, but even the Pro version can't import a Word Table of Contents. That's disappointing, since I use Word TOCs quite a bit. Nisus is, however, a much more agreeable word processing tool than Word. For one thing, the Styles actually make sense.

OS X 10.4 ships with TextEdit which uses a "package" version of RTF, but it's too feature sparse. The version in 10.5 is said to be closer to a true word processor and it has support for Microsoft's XML and the ODF file formats (inherited from 10.5). I've no experience with 10.5 though -- and I won't for months to come.

Pages, part of Apple's iWork suite, uses a proprietary Apple XML file format. That rules it out for me.

The only remaining alternatives are Word for Mac or Word 2003/2007 running in a Win2K or XP VM (VMWare or Parallels).

If all my machines were MacTel and I didn't use Nisus, I'd probably run Word 2003 in my Win2K VM. The tyranny of the .DOC file format should not be underestimated.

Update 2/28/2008: I've unfortunately become aware of Nisus Achilles heel. It can't compress embedded images. So a 3 MB JPEG embedded in a Nisus document produces a 20MB file -- Nisus stores the image as an uncompressed bitmap. Word compresses embedded images, and allows them to be clipped. I'm curious to see what Pages does.

Update 10/13/2008: When I moved my machines to 10.5 I also upgraded to Nisus Writer Pro. I haven't tested to see if it still has the bitmap problem, but it does have other issues. In a document where I used huge fonts (visually impaired user) Nisus was slow to redraw some pages. An image positioned using Nisus Writer Pro vanished when the document was opened in an older version of Nisus Writer Express. I have also become aware of how much I miss a drawing tool layer. AppleWorks drawing tools were particularly good, they really played to the strengths of AppleWork's compound document model. I might take another look at iWork, though that is a return to proprietary document formats. I do wish the rest of the world cared more about document longevity!

Apple's temperature problems: iMac again

This is very disappointing. The 1st generation flat panel iMacs had very serious heat problems, but Apple did come up with a passable redesign. The Intel switch was supposed to make this a thing of the past.

It appears that Apple forgot that lesson rather quickly:

AppleInsider | Freezing iMacs may be victims of hardware, not software

...This and other reports provide increasing support for beliefs that the lockups and related symptoms are caused by excessive heat inside the all-in-one chassis. Users often report graphical corruption in the operating system as a precursor to the freezes -- a sign some PC users recognize of a video card pushed beyond its safe operating temperature. In some instances, the visual artifacts become increasingly likely as time goes on....

Once again, proof that you never want to buy the first generation of any Apple hardware or software product - no matter how glowing the reviews. Apple does not have a "culture of quality" -- so customers need to wait for early adopters to do basic quality control.

SpiderOak: online backup for Mac and Windows

SpiderOak provides online backup, unlimited public file share and differential backup (only changed parts of files). Cost $10/month but limited to 20 GB. Requires a proprietary client.

Interesting, but I don't trust their software enough to expose my machine to it. I'll keep an eye on them though, maybe when they've been around a while ...

It's a bit odd that they don't tell you how to sign up for their free 2GB service. I suspect it's done through the client but they might mention that. I suspect they'll clarify that omission pretty soon.

Microsoft LifeCam software progress: now the blue screen can't be read

I bought a Microsoft LifeCam VX-6000 over a year ago. That was before I realized the quality consumer desktop videoconferencing market was dead on Windows. (Ok, there may be an rare exception.)

At the time it installed without a problem on my home XP machine, but on my Dell Latitude D620 it was another story:

Gordon's Tech: Microsoft LifeCam VX-6000 - personal impressions

... On my pure, clean, office laptop however, it produced the XP Blue Screen of Death (STOP error) on launch. I don't remember ever seeing the XP BSOD. I think it's produced by an 'inner ring' memory error, something that only device drivers can do...This is what one sees in white on blue text:

A problem has been detected and windows has been shut down to prevent damage to your computer ...
STOP: VX6000xp.sys
kmixer.sys

Happens every time on launch of LifeCam (is it doing some kind of dynamic device driver hack?). When you get these errors, btw, you get to file a special bug report with Microsoft on system restart.

I restored the system to health per Microsoft troubleshooting recommendations:

System restore: restored to the point set by the LifeCam install.
sfc /scanonce: ran sfc.exe to verify core XP files were intact. See xp resource kit, system file tools

I'll try again in September when Microsoft says they'll put the installer files online.

Well, I didn't get back to it in September 2007, but I tried again today, 13 months later. I downloaded the latest XP SP 2 LC 1.4 installer.

I'm pleased to report that Microsoft has made a lot of progress in the past year. Now the blue screen vanishes so quickly it can't be read, and the system doesn't let me generate a bug report on restart.

I think there's something buggy with the video in my Dell laptop. Once again I miss my Macs.

I wonder if Microsoft is going to decide they need to buy Dell and emulate Apple ...

Windows Live Writer is out of beta

The best blogging tool on any platform is now out of beta:

Finally Final! « whateverblog

We’re thrilled to bring you the final version of Windows Live Writer 2008–our first non-beta release!

It's an excellent product. Ecto 3 beta is probably the closest OS X alternative, and it's much less robust than WLW (editor is buggy, it doesn't download a full tag set, etc).

Free, too. I use it extensively with Blogger and Sharepoint 2007.

Don't miss the Firefox integration. (Unsurprisingly that doesn't appear on the Live.com page, but surprisingly it does exist.)

OS X 10.5 Leopard firewall really is broken

I thought the early reports might be exaggerated, but it really is broken:

TidBITS Safe Computing: Leopard Firewall Takes One Step Forward, Three Steps Back

...These are all problems Apple is perfectly capable of fixing and I'll be surprised if they don't address them sooner rather than later. Until then, I still recommend you activate the firewall in Block All Incoming Connections mode so you don't break applications. If you need to enable file sharing or other remote access, you'll need to either select the Set Access method, or turn your firewall off. One last option is to use ipfw and manually configure firewall rules, or use a GUI tool like the free WaterRoof, and skip the Leopard firewall completely. In WaterRoof, just click Rules Sets to pick your rules, and then go to Tools > Startup Script and install a startup script to run those rules when you reboot.

I originally thought I'd go to Leopard with 10.5.1, but now I'm settling in for a significantly longer wait. Maybe 10.5.3. It looks like I was right last February when I guessed they were a year away from ready.

iPhoto 7.1 (iLife 2008): better except for the red eye

After a few months of intermittent use and two weeks of regular use, I think  iPhoto 7.1 is quite a nice upgrade. Apple fixed a lot of iPhoto annoyances, though they again decided not to support Library merges.

There's one odd regression however. Red eye correction in previous versions of iPhoto was great -- significantly better than Aperture in my hands.

Now it closely resembles Aperture's red eye correction -- and I don't like it. Pupils are showing odd dark gray blobs rather than a reasonable facsimile of their true form and color.

Ouch. That's a heck of a regression.