the creative tech writer

The Future of RoboHelp?

The lastest WritersUA article goes deep into truthful speculation territory about where RoboHelp is headed. For amusement, check out the linked Macromedia forum posting by the Middle Manager In Charge. Something tells me her email addy's going to be circulated far and wide, and in the most embarassing places.

Doesn't really surprise me, though, this sunsetting. Tech writers are such a niche market and even in groups they have precious little pull, if any, with regard to corporate purchasing decisions. So, any company that caters almost exclusively to tech writers has its days numbered from the get-go. I can't really blame Macromedia for pulling the plug on it. Not like they were after RoboHelp in the first place. Once they bought eHelp, RoboHelp was just in the way and the potential alienation of one little market segment was viewed as an acceptable loss.

And it doesn't really surprise me that Macromedia is behaving as obnoxiously as companies thrice its size (namely Microsoft and Adobe). They've been PR and customer service idiots since way before eHelp slipped onto the radar. I probably would have been off Macromedia long ago, but dammit, Dreamweaver and Fireworks are wonderful apps to use and their developer community has been so very helpful to me over the years. It also doesn't hurt that their employees keep weblogs, though they're not quite as interesting to read as those written by MSFT employees.

Anyone besides me think it amusing that Macromedia is being acquired by the company that sued it for ripping off their interface? It makes me wonder if and when MSFT implodes under its own weight, will Apple be there to cherry-pick merrily among the ruins? Sure, when Steve Jobs and Bill Gates become old-fart drinking buddies reminiscing every Friday night about the good old days of being paid obscene amounts of money for having naught but their name and a ripping good god complex.

Assuming they each survive their disciples' disillusionment.

Hey, it could happen.

Posted by Jenny at 10:32 PM | Permalink | Comments (0) | TrackBacks (0)

3DGPU.com : RoboHelp 'Sunset', MadCap Announcement

Geez...the minute I stop paying attention to the usual TW info outlets, something marginally interesting happens.

Apparently, some company called MadCap is going to channel the spirit of Robohelp into something called Flare. And apparently, this new company is made up of members of the old company that Macromedia swallowed whole and then spat out the bones.

I don't know about this. On the one hand it's nice to know Robohelp will survive in one form or another since it's been positively languishing in Macromedia's stable of higher ROI apps. On the other hand, I'm incredibly disappointed that no one at the Collective Formerly Known as eHelp Formerly Known as Blue Sky Software could think of better names for the company, first of all, and for the flagship product. Forgive me, but just once I'd like a major Product of Supreme Professional Usefulness to have a sensible name. And too, I can do without sensing the hysterical spirit of the late 90's whenever I see the company logo, hear the company name, or use the company's product.

How bloody retro.

Anyway, from what I see on the MadCap site, Flare looks interesting if only for the addition of XML to the laundry list of supported help formats. Pricing, though, remains to be seen. Nothing out there to try yet, but I did sign up for the Sneak Preview whenever they decide to release it. Of course, if you can't wait that long, there's always the beta tester program.

Nice to see the soap opera of tech writer tools continues.

Posted by Jenny at 08:33 AM | Permalink | Comments (0) | TrackBacks (0)

Chris Praley: Let's talk about Word

Every technical writer's minor fantasy: Finding out how MS Word really became the word processing champ.

Actually, it's the old complacency game -- convince yourself of your own importance and you open the door for someone else to one-up you in a big way. Doesn't matter if your product works like your equally complacent customers want it to or that it's "the standard." Someone else will do something similar, cheaper, quicker, and in some cases better. Hmmm...sounds like a professional lesson.

Posted by Jenny at 11:34 AM | Permalink

OpenOffice.org Off-the-Wall: Style Is Everything, Right?

TECHWR-Ler Bruce Byfield sets the Linux crowd straight on using styles in OpenOffice.org.

Posted by Jenny at 10:11 AM | Permalink

WikiWiki as Tech Review Vehicle

I know of some tech writers who've used wikis with some measure of success for doc development. I haven't used it myself yet, because I don't have a whole lot of trouble getting reviews, even if they are cursory. I generally make it known that "no comment" implies unconditional acceptance (and therefore joint accountability) by default, and so far it's worked. But then, too, the company I work at is much, much smaller than Microsoft.

Still, I love reading about others' experience with it. Hopefully, Koby will keep us posted about wiki acceptance on the VSS team.

Posted by Jenny at 09:11 PM | Permalink | Comments (1)

SourceSafe for non-Software Developers

Nice little article about how Microsoft's Visual SourceSafe is supposed to work and, indirectly, how it doesn't necessarily work for non-software developers, such as technical writers.

Continue reading "Uncontrollable Source Control" »

Posted by Jenny at 08:47 PM | Permalink

New Scientist: Advanced Chip Opens Door to Software Choice [via LucDesk]

Nice article about Intel's plans for a processor that lets you run more than one OS simultaneously. Definitely would be more convenient than reconfiguring a machine to dual boot between, say, Windows and Linux. And it would interesting to see how the computing playing field leveled out if people could operate a Mac OS alongside Windows. Thus, the article heralds a new era of software choice for all.

But....

The thing I've always found interesting about the concept of "software choice" is the amount of responsibility that goes with it -- specifically, the responsibility of maintaining a technical knowledge level well above the Dummies books. I know of only a handful of tech writers who actively pursue this objective. And I know of no one who does this for any other reason except for work. It might be enjoyable, but it's still work.

Continue reading "A New Hope?" »

Posted by Jenny at 11:00 AM | Permalink | Comments (1)

Managing and Documenting Your Project XML Style [via Software Documentation Weblog]

An interesting article about using XML to single-source project documentation for use in project management apps as well as for direct outputting to PDF and HTML. Hardcore tool junkies will probably yawn since the article only highlights about 3 tools. But those who go for something leaner might get a little tingly inside.

Posted by Jenny at 08:19 PM | Permalink

Oh yeah, before I forget....

One of my favorite software makers is acquiring one of my least favorite software makers. You guessed it, Macromedia is swallowing eHelp. Whether they decide to chew first is entirely speculation at this point. But I bet it's safe to say that overall pricing won't change all that much. As some on TECHWR-L have pointed out, perhaps the makers of Dreamweaver can do something about RoboHelp's characteristically dodgy code -- Hello, 1997 called, they want Frontpage 1.0 back.

I think the most immediate benefit to this merger will be better-written sales emails. eHelp has been rather intent on keeping its reputation as the most obnoxious software company on earth in terms of sales and support. I mean, what other company besides Microsoft would have the cheek to claim they are "worldwide leaders in award-winning software?" Macromedia's been a bit more relaxed about closing the sale. A friendly email saying "Hey dude, your trial's, like, about to die, man" and that's it. You buy, you buy. You don't buy, you'll very probably be back later.

Long term, however, I'll be very interested to see how Macromedia treats eHelp's love children. Will they be whipped into sullen-faced servitude -- lean and mean but fundamentally crippled -- or will they be allowed afternoon exercise, tea, and a story before bed...that is, thoughtfully maintained and relevantly improved? I suppose we'll see soon enough.

Posted by Jenny at 01:08 AM | Permalink | Comments (1)

Software Documentation Weblog: xCHM 0.8 released

A while ago I posted about a HLP viewer for Linux. Well, now Lars Trieloff reports that an open-source CHM viewer for the platform is now available.

According to the developer:

"xCHM can view your files, show the contents tree if one is available, print the current page, work with bookmarks and do the usual history stunts. It allows you to change fonts and search for text in all the pages of the archive, or in the pages' titles. What it can't do is handle Javascript by the book."

Should be good news for tech writers who are having to create separate outputs for Windows and Linux versions of their apps.

Posted by Jenny at 08:11 AM | Permalink

Open Mind: Getting to know OpenOffice.org Writer

Fellow TECHWR-Ler Bruce Byfield gets his due on the Open Mind blog for his article on OpenOffice.org's Writer. Just in time, too. The piece reminded me I need to upgrade my installation.

Posted by Jenny at 04:54 PM | Permalink

Open Mind: Don't say I didn't warn you...

Joe Brockmeier of Open Mind comments about Microsoft's licensing game and how MS Office 2003 will hold millions of desktops ransom if adopted as blindly as its predecessors.

This was especially interesting to me:

"Since the file format is encrypted now, Microsoft will be able to go after any companies or projects attempting compatibility by threatening them with DMCA lawsuits."

Hmmm...so now I'm wondering how eHelp's coping with this. For straight online projects, tech writers can use Robohelp with no worries. But what about the people who use Robohelp for the help and then output to Word for printing? What about the (presumably) diminishing group of writers that use Word for printed docs that get turned into WinHelp? Perhaps this is what eHelp's "Mustang" product is trying to address, even while it attempts to address Quadralay's WebWorks market? Will the relatively new WebWorks for Word product disappear?

Of course, it may be too soon to start sounding alarms -- upgrades don't usually become significant for a year or so after a new version comes out. At least, that's been my impression with business users. Still, seems like if you were looking for a pressing reason to migrate to WordPerfect or OpenOffice.org, truly obscene lock-in licensing policies should be reason enough.

Posted by Jenny at 07:36 PM | Permalink

A couple of things I'm coming back to when I have a bit of time tonight:

Slashdot.org: Version Control for Documentation?

Via Slashdot, Word Processors: Stupid and Inefficient

From preliminary skimming, it looks like this is a case for separating form from content. Pretty tough talk for 1999.

Posted by Jenny at 03:12 PM | Permalink

Software Documentation Weblog: Windows Help for Linux

If anyone's been wondering how to port their Windows .hlp files to Linux, then wonder no longer. Now that HelpExplorer is here, "porting" per se is no longer necessary. It'll display the .hlp file without any fanfare, in much the same way that Windows would. I think the main difference is that you can customize the interface in development -- I'm not sure that's a good thing, but it's nice to have the option.

And even though you probably have to go through some registration rigamorole to get the download URL, it's free (as in beer) for the asking.

Posted by Jenny at 01:46 PM | Permalink | Comments (1)

Wired 11.07: The Peacemaker

This interview with Linus Torvalds was a pleasing balm to my ruffled conscience today. In particular, I liked this quote:

Another way of putting it: I don't have to doubt myself, because to some degree I don't have to care whether I'm right or wrong. If I'm right, I'm right, and if I'm wrong we can go back and fix it. The only thing you generally can't go back and fix later on is that small detail of trust, which is another reason I'd rather bring these things out in the open, so that people know what I think.

All those who attend the current school of American capitalism could learn a lot from this man.

I just have to wonder, though, if sentiments like this is what truly drives the devotion to Apple among Mac owners. I mean, do Mac users have such a palpable feeling that Steve Jobs et Cie are actively soliciting and honoring their trust with each new Mac model and operating system upgrade? Part of me would like to think so, but if this is true then I'd also have to wonder how observant people are because Steve Jobs just doesn't strike me as an "all there" type of guy.

But that's me.

Still, reading this interview makes me feel like the option of casting my lot in with Linux is a real one, and a good decision.

Of course, I'm fully aware that a sound business model for the Open Source Movement doesn't exist. Movements are political, spiritual or philosophical in origin and intent. Money typically doesn't enter into the equation. The fact that it is starting to now, despite resistance from zealous developers, shows that Linux's teeth are growing.

And that makes me feel good. Not because I'd love to see Microsoft get what they deserve for their immoral implementation of capitalist principles. And not because I'd like to see Apple's kung-fu grip on its intellectual property loosen a bit with licensing agreements. I just really like that people can make money doing what they're most interested in doing. And I like periodically immersing myself in the romantic idea of people making money in a fair, balanced exchange with others who appreciate their labor.

Of course, that romantic idea is efficiently wiped out when I read things like this:

Wired News: SCO Slaps IBM With Injunction

[...sigh...]

So much for human evolution.

Posted by Jenny at 01:39 PM | Permalink | Comments (3)

Well, I did it.

I wiped my hard drive and configured my computer to dual-boot between Windows 2000 and Red Hat Linux 9. To wipe my computer I used one of those hard drive erasers, KillDisk, the freeware version of which only did the 1-pass low-level erase (as opposed to the higher-security DoD-grade erase in the Pro version). But I just wanted to make sure that the drive was empty -- I wasn't recycling.

Then I installed Windows -- no big deal there. After I applied all the updates I made a Red Hat install boot disk since my computer refuses to boot to the CD-ROM regardless of what the BIOS setting is. Linux installation came off without a hitch, all told -- it just FOREVER to do. In my world "forever" equates to about an hour, because this was at 2am and I was dozing off in my chair in between prompts for CDs. But I just wanted to get it over with so I could spend the bulk of the weekend getting acquainted and mapping my Windows experiences to the new environment. This is, after all, my only computer, so I was itching to get it back up and running as soon as possible.

Continue reading "Testing..." »

Posted by Jenny at 02:04 PM | Permalink | Comments (2)

Yeah, the more I consider the alternative (to Windows) OSes that are available, the more I think that Apple's current OS really is where it's at in terms of stability and ease of use. Performance, I think, is a relative beast because one person's "achingly slow" is another person's "blazing fast." And from what I've been reading about Mac hardware and PC hardware, differences in performance seem to be linked to what I call the "Tortoise and the Hare" factor.

Continue reading "Which One Indeed..." »

Posted by Jenny at 10:34 AM | Permalink | Comments (12)

Yep, for the jillionth time, I'm considering OS alternatives to Windows. I'm starting to look more seriously at Linux because I no longer want the responsibility of supporting a software publisher who gets paid to mistakenly assume that he (not to mention the chip maker) owns my machine instead of me and, therefore, can do whatever he damn well pleases at the OS-level behind my back. Dirty pool, to say the least.

Call me crazy, but I consider commandeering of private resources for anything other than life-and-death, emergency situations extremely bad form. So, I've come across some of the major Linux distros and I'm trying to decide which one to use. I'm looking at RedHat, SuSE, Mandrake, and Debian.

Basically, what I want is an OS that installs as gracefully as Windows 2000 does, and looks as good as OS X does. And I want it to function better than either of them. Is this a tall order? I don't know, but I'm hoping find some reviews and some straight talk about the pros and cons of each distro.

Then I have to see if I'll need a new sound card (since I think my current one only operates under Windows). I suppose I could partition my hard drive and test out a distro once I pick one. Right now, I just want to do one thing at a time.

Anyway, if anyone can give me good reasons for or against any of the Linux distros out there, feel free to comment. I'm totally open to recommendations at this point.

Posted by Jenny at 09:11 PM | Permalink | Comments (4)

Changes in Internet Explorer for Windows Server 2003

A significant change:

IE will no longer be a standalone product that merely wraps its few tentacles into the OS. In the future, if you want the newest version of IE, you have to update your entire OS.

So, if you're now slapping the table and cursing Bill Gates' progeny into the next millenium, and you were wondering about using an Open Source browser, might I suggest something in a citrus-fresh Mozilla? Or perhaps you're an SUV-driving, road-hogging, way-too-permissively-parenting soccer mom with tragically romantic early-adopter sensibilities? In that case, you might try Firebird.

And if you've got cash to burn, now's as good a time as any to Make the Switch.

Quickly, now, before Windows starts calling your boss to rat on you for calling in sick on a Friday...

Posted by Jenny at 08:36 PM | Permalink

ComputerGripes.com: Gripes about Open Office

Basically, this gripe is about the many ways in which OpenOffice.org (Writer in particular) does not behave *exactly* like MS Word, and provides supporting evidence that, at this moment in time, Open Source software is Not Necessarily Ready for Prime Time as far as John Q. Clueless-End-User III is concerned.

Duh.

These gripes are pretty much invalid because the griper is judging immature software as if it was a fully developed product.

That's not to say that I don't agree with the gripes cited. Yes, the documentation needs A LOT of work before it can be a trusted resource for users of any skill level. Yes, the software itself needs A LOT of work before it can really give MS Office a run for its money. But at version 1, that's a given -- not only for Open Source software, but for any software product. Apps that work exactly as intended and desired at version 1 are much less complicated and serve the much-narrower needs of a much smaller user base.

So, dude, chill and cut the OpenOffice.org team some slack. Take another look when it's at version 3 and see if any of those version 1 gripes stand up. Better yet, put your money where your spleen is and contribute to the project. You'll find out real quick why version 1 software is what it is and why perfect version 1 software only exists in the Star Trek Universe.

Posted by Jenny at 06:48 PM | Permalink

Yet Another Tech Writer Drama on the TECHWR-L list, this time dealing with who's ultimately responsible (or to blame, as the case may be) for documents.

It all started innocently enough, with an article on keeping docs fresh, or what what the trade likes to call "living documentation." Then, in the space of a few days of back-n-forth-ing, it splintered off into "pros vs. amateurs" and "management vs. the real world" among other things.

And of course, the reason why it degraded so swiftly was because 1) the self-proclaimed pot-stirrer for the list weighed in, and 2) others on the list decided to take issue with him (as usual).

Continue reading "YATWD" »

Posted by Jenny at 01:36 PM | Permalink | TrackBacks (1)