Atlas Shrugged

Sarah O'Keefe / NewsLeave a Comment

With apologies to all, I simply can’t stop myself from using that title.

Quadralay has released their latest incarnation of WebWorks Publisher, now called ePublisher Pro. While under development, the product was code-named Atlas.

Press release

In the FrameMaker details section, you find this:

IntelliStyles […] automatically imports your FrameMaker styles into your WebWorks ePublisher Pro project, establishing a more advanced starting point for your project and saving you time and effort. Based on your project’s native styles, you can use ePublisher Pro’s new Style Designer to develop all of your manual style-based customizations, such as designating paragraph styles as TOC entries, generating page splits, and including special features – drop-down text, breadcrumbs, Related Topics, and more.

This may be good news for fans of the short-lived RoboHelp for FrameMaker from eHelpMacromediaAdobe. It looks as though Quadralay has added many of the features that RHFM users liked best.

Although The Product Formerly Code-Named Atlas has its roots as a FrameMaker converter, Quadralay’s web site indicates that the Word version will be released first.

Word details

The macro language that we all know and, er, love has been replaced with XSL-based processing.

I wish I had written this

Sarah O'Keefe / OpinionLeave a Comment

Laura Lemay writes in her blog:

You know, I was just the other day thinking that as a knowledge worker, PostScript wasn’t fulfilling all my document workflow needs. And that what I really needed was a Microsoft version of PostScript. Based on XML. Yeah. That’s what I need. That’ll really solve all the lingering icky problems that I’ve always had with PostScript, such as….um….

STC next week

Sarah O'Keefe / ConferencesLeave a Comment

I will be at the STC conference in Seattle next week. Each year, the call for proposals comes out with a due date in August (!!) for the next year’s conference. Each year, I debate whether or not to attend. This year, the prospect of a few days in Seattle did the trick. But next year, the location will be a minus (Las Vegas, ugh).

Here’s why I don’t particularly like attending the STC conference:

  • As a speaker, I get $100 off the cost of registration. Given the amount of time required to prepare a presentation, it’s hard not to be insulted. I’m delivering two presentations this year, and I’ll be lucky to net out $1 per hour for my preparation time. That doesn’t factor in the cost of travel and accommodations.
  • If I submit information for the conference proceedings, STC requires that I give up the copyright to those materials. STC then kindly agrees to license the materials back to me (!) if I need to reuse them. As a result, I have declined to provide materials for the proceedings.
  • The cost of providing printed handouts, on which I can keep my copyright, generally exceeds the speaker’s “stipend.”
  • Because proposals are due nine months before the conference, it’s difficult for speakers to provide fresh information. Neil Perlin helps to address this with the Bleeding Edge stem, which is intended specifically for last-minute proposals on new and unusual technologies.

Here’s what I do like about the conference:

  • Great networking. I get to catch up acquaintances from around the world. It’s especially fun to chat with other consultants about business in their neck of the woods. Life as a consultant appears to be the same no matter where you live.
  • Trade show. An excellent place for market research. Every year, I wander through the booths to see which vendors are being ignored and which have people waiting in line to chat. It’s also a good place to spot new entrants into the marketplace. This year, all eyes will be on Macro-dobe. Will there be one booth? Two? Will there be discussion of RoboHelp?
  • Location (usually). During the past few years, the conference has been in good locations with lots of excellent restaurants nearby. Seattle is one of my favorite cities, and the downtown area has some fabulous shopping and eating options. And, if you’re going, don’t miss the Seattle Aquarium.

If you’re attending the conference, please stop by and say hi either before or after one of my sessions. You can find me here:

Clip, clop…RoboHelp rides off into the sunset

ScriptoriumTech / Opinion1 Comment

At the WritersUA conference last March, Macromedia cancelled participation in the trade show at the last minute. Immediately, rumors began flying (although in fairness we have to say that the Adobe/Macromedia merger was not one of the myriad conspiracy theories that emerged). Before the conference ended, a content-free Macromedia statement appeared in a RoboHelp forum at Macromedia’s site.

The apparent demise of RoboHelp matches the general industry trend over the last two years. Technical publishing groups are beginning to demand that tools support open standards (XML and XSL) that offer greater flexibility.

We are being asked to produce more and varied forms of output (beyond the basic print and online help), to share content, and to extend publishing workflows to include other departments and organizations. Software customization based upon user profiles and authorization is creating the need for user assistance that accommodates a complex matrix of variations in both feature sets and user interfaces.

These demands make a transition from proprietary solutions to open standards-based tools quite appealing. Structured authoring based on XML can address all of these requirements, and XSLT is quickly becoming a popular tool for transforming data from a broad variety of applications. This is where many of our clients are moving and we are adding classes (XSLT) and offering products (DocFrame) to meet the demand.

Metro, Tube, Underground, El, Subway, PDF Killer?

Sarah O'Keefe / NewsLeave a Comment

News from the Windows Hardware Engineering Conference:

Officially unveiled as part of Microsoft Chairman Bill Gates’ kick-off keynote, the new Microsoft document workflow format, code-named ‘Metro,’ sounds from initial explanations like a page-description language meant to compete with Adobe’s PostScript.

Microsoft to Pit ‘Metro’ Format Against Adobe PDF, PostScript? (

All of this is still smoke and mirrors, but a few interesting tidbits do emerge from the presentation:

  • The Metro page description language is XML-based.
  • Metro is supposed to provide files for a print spooler (similar to PCL or PostScript) and an application-independent page-description language (similar to PDF)
  • Metro’s license will be royalty-free to “encourage adoption.”
  • Metro Specification and FAQ

When Adobe introduced PostScript about 20 years ago, desktop publishing was just getting started. The idea of being able to print production-ready documents from the desktop was revolutionary. Today, we expect perfect print fidelity as a matter of course. The window of opportunity for introducing, field-testing, and debugging a page description language may have closed.

So, what does Microsoft do? They introduce Metro as part of their operating system. In Longhorn, the print spooling service will use Metro files.

I don’t know whether to be appalled or impressed. Does the expression, “If it ain’t broke, don’t fix it,” ring a bell for anyone in Redmond?

Democracy. It’s a beautiful thing.

Sarah O'Keefe / NewsLeave a Comment

Each year, the Nominations committee of the Society for Technical Communication (STC) holds elections. The process is well-ordered:

  1. The current first vice president runs for president.
  2. The current second vice president runs for first vice president.
  3. The Nominations committee selects two people to compete for the slot of second vice president.

In order to become president, you must win one election — for second vice president — two years before you actually become president. To be eligible for that election, you must get the nod from the Nominations committee.

This year, things got shaken up. Instead of two candidates for 2nd Veep, there were — gasp — THREE. How did this happen? There were two candidates with the official seal of approval from the Nominations committee. And then there was a third candidate, Paula Berger, who went through a tedious petition process to get her name put on the ballot after being, well, un-selected by the Nominations committee.

I’m sure it comes as no surprise that Paula has now won the election for second vice president of STC:

STC election results

After all, only Paula had to recruit several hundred individuals who were interested enough to sign her petition. And having signed the petition, you figure that they definitely voted!

Congratulations, Paula!
(I did sign the petition and vote for her.)

Development, yes. But content management?

Sarah O'Keefe / OpinionLeave a Comment

The Adobe/Macromedia is now being described as a content management play:

The friendly acquisition of Macromedia by Adobe bodes well for both companies: Adobe has been perceived as lacking direction in recent times. It has steadily built up its document management capability, helped by the previous acquisition of Q-Link in 2004, which added workflow capabilities to its document process management solution, known as Intelligent Document Platform. However, it has seemed out of touch with the movement elsewhere in the market, particularly in Enterprise Content Management (ECM), where large players have been busy consolidating.

The situation with Macromedia was the reverse, in that it had a clear strategy in offering advanced tools for Web page and application creation, built around the ubiquitous Flash engine, in anticipation of a growth in [rich Internet applications].

CommentWire by Datamonitor – Adobe / Macromedia: strategically positioned for content riches

I’m a little confused by the reference to content management. Neither Adobe nor Macromedia has an enterprise content management solution at this point. Both are mainly focused on content development. I think that getting into content management would be an excellent idea for the combined company, but I fail to see the current relevance of content management to this merger.