Random thoughts about publishing

icon Site Feed

Labels

Acrobat DITA Open Toolkit DITA XMetaL FrameMaker DITA__TechComm DOS DRM Flash FrameMaker InDesign Microsoft Word PDF Photoshop RSS feeds STC SWF SnagIt TechComm Suite Twitter XSL DITA OT customizing specialization XSL DITA OT customizing specialization.php XSLT accessibility adobe analysis apostrophes blogs book business cake change management cmd comments concerts conferences cowbell cranky dita ditalini recipes potluck dita ditalini doctrain doctraineast07 doctraineast08 doctrainwest08 documentation drag and drop ePublisher Pro entertainment equations fish flare framemaker review free garlic georgina's gilbane08 globalization graphics WMF green hacking history humor is08 jobs localization madcap music outlook oxygen path names podcasts potluck predictions presentations print on demand publishing punctuation quark ratings recipes regular expressions reviews robohelp screen captures secured PDF specialization stc09 stc2008 structured authoring survey techcomm alliance technical writing tekom thirst for knowledge thunderbird toc2007 trademark training travel unspoken rule user group video games volunteering vote citizenship rights weather web 2.0 webcasts white papers wiki writersua2008 xmetal xml strategist xml xpubs xsl-fo xsl

Palimpsest

 

eWeek analysis of TC Suite

Tuesday, September 25, 2007 — posted by Sarah

They misspelled Michael Hu's name, so minus points for sloppiness.

Introducing: Adobe's Software for the Technical Writer (eWeek)

I have some issues with this article. For instance:

I think the addition of support for Flash into Acrobat is important -- it will allow us to create much more interactive PDF files. But I'm afraid that I'm not quite on-board with the hyperbole from Adobe (sorry, Mike)?
"We're going to change the dynamics of this industry and change how people are creating content and change how people consume this content," Wu [sic] said.
Here is the unauthorized translation:
This TC Suite is going to hurt our competitors, who are all providing point solutions. Even if you concede that, for example, Flare might be better than RoboHelp, when we put FrameMaker and RoboHelp in a single box with an attractive price point, it makes purchasing FrameMaker and Flare separately less appealing.

ePublisher Pro's integration with FrameMaker is probably better than RoboHelp's, at least for now, but licensing RoboHelp as part of the Suite is going to be much easier than justifying two separate purchases.

If we can piggy-back Captivate onto the big authoring tools (FrameMaker and RoboHelp), we'll get incremental revenue from people who might have otherwise not bothered with buying a simulation tool.
In short, the losers are going to be:
Lots of Captivate competition on that list. Makes you wonder if this is really about Flash and Acrobat, rather than FrameMaker/RoboHelp integration.

And one other random note: MadCap already has a suite called MadPak, which includes Flare (help authoring), Mimic (simulation), Capture (screen captures), and Echo (audio). No great print solution, though.

Labels: , , ,


12:57 PM Permalink | |

<< Home

divider


Scriptorium Publishing | Post Office Box 12761 Research Triangle Park, NC 27709 | (919) 481 2701 | info@scriptorium.com