Previous Issue | Search TidBITS | TidBITS Home Page | Next Issue

TidBITS Logo


In this week's installment of Hacking the Press, Adam sheds more light on the inner workings of the computer media with an examination of different types of editorial coverage. We also recap a pair of TidBITS events at Macworld Expo, announce a new sponsor, and take a quick look at icWord, a $20 utility that lets you view and print recent Microsoft Word documents. Finally, we offer another quiz whose results could improve your productivity!


Copyright 2000 TidBITS Electronic Publishing. All rights reserved.
Information: <> Comments: <>

This issue of TidBITS sponsored in part by:

MailBITS/14-Aug-00 Sponsoring TidBITS -- In the information-scarce days before the Web, I pored over computer-related publications, and even though I've never been a designer, I especially liked font catalogs. They featured impeccable design, with the sample letter forms standing out clean and black on the white paper, all supported by a paragraph of text extolling that font's lineage, virtues, and uses. It's been a long time since I saw a font catalog, but I've equally enjoyed the Web site of, whom we'd like to welcome as our newest sponsor.

As with the catalogs, revels in typography, providing biographies of famous type designers and font descriptions. But what gives its appeal is its dynamism - the entire site is backed by a comprehensive database that lets you start with any font and see more typefaces by the same designer, foundry, or vendor, plus other faces that are visually similar. The TypeXplorer tool takes this browsing to the next level for most fonts, letting you ask to see similar typefaces that vary by boldness, width, contrast, or x-height. You can see the full character set for any font, plus enter a limited amount of your own text to see how it looks. Another tool called WhatTheFont (previously called Identafont) will try to match an uploaded scan of text to fonts in the 10,000 font database.

Like other Web sites that give you a window into vast databases of information, such as the Internet Movie Database (IMDB), is just plain fun if you're at all interested in typography. And if you're a design professional, you can buy many of the fonts you find in Either way, I think you'll enjoy spending some time browsing around [ACE]


icWord Reads and Prints Word Documents -- Panergy Ltd. has released icWord, a utility for viewing and printing Microsoft Word documents. Targeted at people who need to access, but not edit, Word files, the $20 program is far cheaper than the $400 Word 98 or the $500 Office 98 bundle of Word, Excel, and PowerPoint. icWord can open and retain the formatting for files created in various versions of Word for both Macintosh and Windows (though Word 4 or Word 5 for Macintosh); it can also specify substitute fonts to be used when the original typefaces aren't available. icWord has the added capability to extract and view Word documents encoded in StuffIt, Zip, uuencode, and BinHex files. In our initial testing, icWord displayed most Word documents correctly; if all you need to do is look at or copy text from the occasional Word file, icWord is the utility for you. icWord requires System 7.1 or later with 8 MB of free memory; a 1.3 MB 30-day demo version is available. [JLC]


Quiz Preview: Bigger is Better -- When the Mac debuted in 1984, it featured a 9-inch black and white display that was 512 pixels wide and 342 pixels high, and the density and graphical fidelity of that display compared to other computers was part of the Mac's eventual success. These days, iMacs have 15-inch displays and default to a resolution of 1024 by 768 pixels; a logical display almost four and a half times larger than the original Macintosh. Plainly, a larger display with a greater display area is beneficial because you can see and do more simultaneously. So, this week's quiz asks what you can do to see more on your Mac's desktop. We'll give you a hint: it doesn't necessarily involve acquiring a new Mac, a new monitor, or new add-ons - or even installing software. Test your knowledge on our home page, and we'll cover the correct answer next week! [GD]


Poll Results: Rumor with a View -- The results of last week's poll, which asked if you thought the value to consumers of information published on rumor sites outweighed the potential damage done to the companies involved, proved mixed. Of more than 800 responses, 62 percent felt that the value did not outweigh the potential damage, 38 percent felt it did. More interesting was the TidBITS Talk debate, in which some people argued that companies got what they deserved because they often intentionally leaked rumors, that sales weren't lost thanks to rumors, and that the real value of rumors was in helping people time purchases for the optimal bang for the buck. Also mentioned was the correction to the article "Apple Gets Serious about Plugging Leaks" that the classic case of a company dying because of rumors was Osborne, not Kaypro. The post that gave me the most to think about, however, was one from Doc Searls (senior editor of Linux Journal and co-author of The Cluetrain Manifesto) that hinted at the utility of open source attitudes in corporate dealings for the benefit of both consumers and vendors. Recommended reading. [ACE]


TidBITS Expo Events Recap

by Adam C. Engst <>

As readers of TidBITS Talk know, I held a pair of informal events at Macworld Expo in New York last month. I chose not to announce them in TidBITS itself (though they were on the Hess Events List) to keep them to a manageable size.


Ice Cream Social -- Tuesday night before the show, I coordinated the TidBITS Ice Cream Social, where everyone met in the lobby of the aggressively hip Paramount Hotel and then walked to a nearby Ben & Jerry's for ice cream. The staff seemed slightly put out at a group of 36, but after trying to driving us out by cranking the music, they gave up. (Luckily, we'd all finished our ice cream by the time I decided it would be polite to cede the store to a just-arrived crop of girls wearing Barbizon School of Modeling t-shirts.) Many of us ended up back at the Paramount lobby, where we commandeered the Paramount's unusual chairs for several hours. The Paramount folks asked us not to take pictures of the lobby, but Pekka Helos of the Finnish MacMaailma magazine got a few pictures of the group outside. Pekka wasn't the only international attendee - Philippe Lopatka came from Switzerland and Dave Fitch from Scotland. A pair of our translators were also able to make it - Jacques Germans of the Dutch team and Elana Pick, who has helped with the Russian translation. It was an unqualified success, and we'll definitely continue the tradition.


Underground Tour -- In the morning of the last day of the show, I led a 90 minute tour of Macworld Expo for a small group of about ten people. I had literally no idea how it would work out, but figured that we'd cruise the floor together for a while, looking at interesting booths and talking with some of my industry contacts. The random floor cruising was difficult with a group of that size and ultimately unsuccessful, but the informal meetings I'd set up for the group worked extremely well. We first stopped at the Main Event Software booth, where Cal Simone, president of Main Event and one of the Mac world's top AppleScript experts, showed off his new Scripter Personal Edition, an AppleScript authoring tool that makes getting into AppleScript far easier than Apple's minimalist Script Editor. Then, at the booth of TidBITS sponsor Dantz Development, Dantz's vice-president of marketing, Craig Isaacs, gave us an overview of what was new in Retrospect 4.3 and what we could expect from Dantz when Mac OS X became available. Finally, Jeff Robbin, one of the authors of Casady & Greene's SoundJam MP, demoed SoundJam, chatted about what he was working on for the next version, and even graciously accepted an interface suggestion regarding SoundJam's alarm clock feature.


In fact, the tour reflected closely how I do the floor at a trade show - I wander up and down the aisles looking at booths and products until I meet someone I know, which then requires a fifteen to twenty minute conversation. It's great fun and extremely useful for my line of work, but I ended up frustrated that I hadn't been able to cover more ground with the tour. Plus, if all of the 25 people who had signed up had actually come, I think the group size would have been unwieldy.

I'll continue to think about better ways of organizing tours for future shows, and I suppose it's appropriate if the tour ends up working like TidBITS, where we're happy to write longer articles to cover topics in depth. Keep in mind that in any case where space is limited, I'll probably announce first to contributors and on TidBITS Talk before opening an event up to the full TidBITS audience. Just another reason you might want to check in on TidBITS Talk in email or on the Web.


Hacking the Press, Part 3: Types of Coverage

by Adam C. Engst <>

Welcome back to my series of articles on how the press works and how to work with the press. I first talked a bit about why you should care about press coverage, and I followed that up with a discussion of different types of publications. This week I'll turn to the types of coverage you can expect.


Whenever we write a review of a program that has significant competition, we immediately receive email asking why we didn't compare the program with its competitors. Our answer, each time, is that the article was a review, not a comparison. I always feel bad about saying that, since it feels like a cop-out, but the fact is that every publication chooses to publish different types of articles depending on the situation. Let's work through them, starting with the smallest and least considered, but by no means the least important.

Mentions -- When thinking about article coverage, few people stop to consider the mere mention of a product or company, perhaps in a large feature article or even in a review of a competitor. If it happens to you, your product, or your company (for simplicity's sake, I'm going to abbreviate these three possibilities to "you" from now on), you may not even notice. After all, the article wasn't about you, so what difference can a few words make?

Actually, a mention is one of the most powerful and useful forms of coverage you can get, and it's an indication of success. When it comes to press coverage, being ignored is a bad fate. The fact that you rate high enough to warrant a mention often means one of several things:

So don't underestimate the utility of small mentions. They don't carry much information, but what's important is that readers will think of you in that context. There's little you can do to ensure that you're mentioned other than cultivate your relationships with journalists and work on a solid advertising and PR strategy aimed at making your name well known.

News Blips -- "News blip" isn't a technical term, but I'm thinking about the kind of news coverage that can be condensed into a sentence or two. Publications often use news blips as a way of increasing timeliness and breadth of coverage, since it's easy to throw in a news blip about a product or company that wouldn't otherwise warrant coverage.

Readers like news blips because they're easily digested and give an overview of what's happening. Web-based publications like MacCentral, MacInTouch, MacFixIt, and MacNN, and even headline sites like MacSurfer draw much of their popularity from their frequently updated news blips covering recent events, product releases, and reader reports.

Single news blips are easy to produce, but the cumulative effort of posting numerous news blips each day is huge. Just sorting through incoming email and scanning other publications (yes, everyone does it - it's a time-honored research method) is a brain-busting job, and writing up the results day in and day out requires true grit.

Thus, anything you can do to simplify news blip collection and production efforts will increase your chances of coverage. That boils down to creating effective press releases that contain all the necessary information. Although you should never baldly state this, a well-written summary paragraph at the top of your press release just might find itself becoming a news blip at publications that are under especially high time pressure or that don't feel the need to write everything from scratch. One warning: don't invent or overinflate events (like beta releases) just so you can put out a press release and get news blip coverage. It may work for a while, but it's essentially a modern-day equivalent of the fable of the boy who cried wolf.

Although I don't deny the popularity of news blips, I personally find them less useful than brief mentions because publications specializing in news blips often aim to be comprehensive instead of selective. More and more, I find that I prefer sites or publications - not just in the Macintosh world - that drill down on specific topics. So, when making decisions about where to focus your efforts, aim first at publications that are targeted to your desired audience, then move out to the more general publications.

Product Announcements -- Next up in the arena of coverage is the product announcement, which many readers confuse for a review. A product announcement is essentially a news item that the publication wants to publish before there's time for a formal review. People often confuse product announcements and reviews because a good product announcement brings together a fair amount of information and provides context and advice. A good reporter can even include negatives from early user comments or knowledge from a public beta to balance the positive information from the announcement. Although publications easily differentiate between the two, the fact that readers may not can be to your advantage.

Product announcements tend to be positive because most of the information comes from the company. Any negatives included are less likely to be serious or specific since the writer hasn't yet been able to work with the final version of the program for long. So, when releasing a product, make sure your Web site has plenty of the kinds of information reporters can use to turn a news blip into a product announcement - what's new and what's cool. Plus, if you have relationships with specific reporters, it's worth giving them - independently - a bit more in-depth information about particular features you especially like. That effort will increase your chances of receiving a better and more detailed product announcement article, and reporters like being able to set their stories apart.

Reviews -- In theory, a review is the ultimate coverage you can receive, since it's devoted entirely to your product, with the only distractions being occasional mentions of the competition. I say "in theory" because reviews have a number of gotchas.



The best way to increase your chances of being reviewed in a publication is to send review copies (also called "comp," for "complimentary," and "NFR," as in "Not for Resale" copies) or software registration numbers to the publications you want to review your product. (But don't assume that sending a review copy entitles you to a review - it just increases your chances.) The cost in sending review copies is essentially nil in relation to the sales a review can encourage, and you want to do everything you can to ease the logistical aspects of a review being written. If you're asked for a review copy by a publication, agree graciously. There are few things journalists hate more than nagging for review copies, and reviews have been cancelled because of vendors being difficult about review copies. In many cases, reviewers don't plan to use the software after the review - writing about products is just a job, and having the software afterwards is seldom a significant bonus. For instance, I did a feature article on cross-platform issues for Macworld that resulted in 18 boxes and 10 loose CD-ROMs. They were mostly necessary for the review, but you know what I'm left with now? Another four feet of software boxes on a shelf that I may never touch again (even if I cover the topic again, I'll probably need new versions).

An important (but often overlooked) flip-side to sending review copies is promptly following up with answers to the writers' questions or concerns about the product. If you don't respond to a reviewer's questions, the likelihood of getting coverage drops toward nil. Since good reviewers tend to look deeply into a program to anticipate readers' concerns, the questions can often help you by highlighting areas that need future development attention. It's best to be straightforward with your answers; don't view each question as an attack on the product since defensiveness may cause the reviewer to focus even more on the feature in question.

Many companies also provide detailed reviewer's guides. I'm of two minds about these - I suspect they're somewhat effective or the companies wouldn't bother, but at the same time, I find them slightly insulting. As a professional reviewer, I should be investigating the program on my own or in concert with other users, not by working through a reviewer's guide. If you're debating whether to invest significant work into creating one, I'd suggest that you restrict your efforts to a one or two page summary of the program's highlights. Reviewers can then use that to make sure they haven't missed anything, but they won't feel as though conclusions are being suggested.

Comparisons -- Readers like reviews, but they like comparisons even more. Where a review aims to tell you whether or not you should consider buying a program, a comparison eases the decision even further by laying out the similarities and differences between competing programs.

The problem with comparisons from the reviewer's standpoint is that they're hellishly difficult because they require that reviewers simultaneously acquire and become familiar with multiple programs, then keep all that information in their heads as they write. Comparisons also aren't as popular with the companies whose products don't come out on top - in a review there's still a chance the user will decide the product is worthwhile, whereas there's less to debate in a comparison. Worse, comparison articles tend to be too long for many publications, and despite their length, there's less room to examine any one program in depth.

One place you might direct efforts with regard to comparisons are Web sites that publish only specific comparisons - I noticed some of these recently while comparing the TiVo and ReplayTV digital television recorders. If you ever run across a site that maintains such a comparison, it's in your interest to work with them to make sure all the information about your program is correct, although it's dangerous to comment on details about your competition.


Feature Articles -- Whereas most everything we've discussed so far revolves around products, feature articles instead focus on topics. I've written a number of features for Macworld on topics like backup, email programs, and cross-platform issues, and in each case, I talked not only about numerous products but also about usage strategies, pitfalls, and other universal aspects of the topic.

My comments above about mentions apply well to the kind of coverage you can expect in a feature, since you're unlikely to be the focus of the article. Any appearance you make in a feature is a good thing, since it legitimizes you in the topic being covered.

It's worth repeating the importance of maintaining good relations with writers and editors. Many writers contribute to several different publications, which are all looking for fresh angles on existing hardware and software. If your product has added a new capability that crosses into a different category, it's more likely to be mentioned in a feature article. For example, there wasn't much to say about the Mac desktop PIM (personal information manager) market for several years until new Palm synchronization capabilities opened up an entirely new editorial category in which PIMs could be mentioned.

Ratings -- Some publications assign ratings to products covered in reviews, comparisons, and features - Macworld took over the mouse ratings after merging with MacUser, and MacAddict has the little "Freakin' Awesome" guy. Ratings work well for readers as a summary of the writer's opinion of your product, and being able to slap a good rating on your box or Web site only helps. However, ratings are tricky for a number of reasons.

You can't argue with a rating, and trying will only irritate everyone. Your best strategy if you receive a lousy rating is to release a revision that addresses the problems raised in the review and ask the publication to look at the new version. Even if you don't get a full review, they may redo the rating.

We had some discussion on TidBITS Talk recently about starting a ratings system for TidBITS. In the end we decided it didn't fit with our editorial approach, but the conversation was fascinating.


Tech Support/How-To -- I'm clumping tech support and how-to articles together because they both focus on a specific aspect of your program. Publications generally restrict this sort coverage to the important programs that they think many of their readers are likely to use; as a result it's great to find yourself receiving such coverage because it means you're sufficiently important to warrant such a look. Even if the article talks about a task your program doesn't do well, it probably also offers a workaround.

There's little you can do to influence this sort of coverage, with the possible exception of passing on clever tips with your software to writers. If they think a tip or trick is sufficiently useful, it might become an article.

Editorial Analysis & Opinion -- I've saved the fuzziest sort of coverage for last - these are the sort of articles where a writer spouts off on some topic or another. Much of my writing falls into this category, since I like to explore topics and attempt to explain them. From the point of view of a developer, this sort of coverage might be great or it might be awful - since these sorts of articles are couched largely in the experience and knowledge of the writer, they vary widely in quality and insight. Thanks to the Internet, everyone can express their opinion, and believe me, there are differing opinions of varying quality on every side of every issue.

I've hammered on the utility of relationships throughout this article, but good relationships are never as important as when affecting editorial coverage. Look at it this way: you want to be mentioned in appropriate analytical or opinion pieces, and you want those mentions to be positive. If you have no connection with the person writing such a piece, the chance of a mention decreases, and the chance that any such mentions will be negative increases. In contrast, if you have a relationship with a writer, he or she is more likely to think of you when looking for quotes or giving examples, for instance, and if you've made sure that person's knowledge of you, your product, and your company is accurate, you're less likely to suffer from a misinformed example. From the writer's point of view, having accurate information helps avoid unnecessary comments and corrections.

Having a relationship with a journalist also gives you some additional leeway in pointing that person at topics you think need coverage. It's usually a bad idea to say, "Hey, you should write about such-and-such," since that may raise journalistic hackles. But there's nothing wrong with forwarding a piece of email about the topic along with a short note explaining why you think it's interesting. Who knows - it might turn into an article with you at the center.

That's it for this week's coverage of these rather broad classes of press coverage. I realize I've set myself up for the big question of just how you should go about establishing relationships with journalists, and that's where I'll turn my attention next.

Non-profit, non-commercial publications and Web sites may reprint or link to articles if full credit is given. Others please contact us. We do not guarantee accuracy of articles. Caveat lector. Publication, product, and company names may be registered trademarks of their companies. TidBITS ISSN 1090-7017.

Previous Issue | Search TidBITS | TidBITS Home Page | Next Issue