RSS FeedArticles
Tuesday, January 01, 2008
Creating DITA Content: Who Says You Can’t Use Microsoft Word?
By Scott Abel, The Content Wrangler
It’s a fact: Microsoft Word is a word processor. Two more facts. Microsoft has not marketed Word as an XML editor. And, they don’t plan to. Why? Because MS Word is not an XML authoring tool, no mater what your IT team—or you—may believe. While Word may indeed understand and use some XML, it doesn’t use XML in the way technical communicators need it to. Instead, it uses XML to transfer information back and forth between MS Office products. Useful? Yes. Structured XML authoring? Not even close.
That said, it’s also a fact that XML authoring tools like XMetaL and Arbortext can do what Microsoft Word alone cannot (even in the newest version of MS Office for Vista). But that doesn’t mean you have to switch to a totally new XML authoring environment in order to enjoy the benefits of XML. Nor does it mean that your staff will need to continue creating documentation the old-fashioned way. A new breed of tools - called XML word processors - can help you develop structured XML content (even DITA content!) without the need to switch to a new, unfamiliar XML authoring environment.
One such product is XPress Author for MicroSoft Word, an authoring tool that empowers writers to create structured XML content by providing a “guided authoring” environment inside the familiar MS Word interface. XPress Author, created by Microsoft partner, In.Vision Research, hides the scary stuff from authors and minimizes changes to the content creation process. The software provides authors with a sense of familiarity and security by leveraging the power of the familiar Word interface.
Authors who don’t need to be down in the XML trenches will undoubtedly find the product easy-to-use. Because the authoring environment is Microsoft Word-based, the change management issues normally associated with moving to XML authoring are minimized.
Tools such as XPress Author provide organizations with the ability to leverage XML across the enterprise. Everyone in the content production food chain—from administrative assistants to CEOs—can create XML content without ever learning about things like DITA, XSLT, and ANT.
Given the sheer volume of knowledge workers who use Word around the globe, there’s likely to be a HUGE market for a tool like XPress Author for Word. If you’re interested in learning more about the tool for use in your organization, let me know. We’re hosting a free, one-hour webinar later this winter that should help you better understand your XML authoring options.
Filed under: DITA : Technical Writing : Authoring Tools : Xpress Author for Word : XML
Comments
Recent articles
Moving Legacy Content To XML: Affordable, Self-Service Analysis/Modeling Tools Needed, Survey Says
Ware are You? Web Content Delivery Strategies
Information Architecture for My Office
Plain English Videos From Common Craft Make Understanding New Technology Easy
U.S. Federal Government Silences Typo Spotters; Forces Them To Stop Encouraging Others
Twing.com: Searching Online Forums and Communities Just Got Easier
Subscribe: Direct Inbox Delivery
Get The Content Wrangler Newsletter delivered straight to your home or work Inbox. It's full of content goodness.
By Marcus Carr on January 10, 2008 -- 6:23pm
There has always been a desire to create structured data from Word and in fact Microsoft had a brief attempt at creating an SGML product in the 90’s. The problem with continuing to develop products along these lines is that they ignore the fundamental shortcoming of not being able to support proper collaboration. As long as people are working on personal versions of files, even if they’re creating good structure, they may not be creating the quality of content that they ultimately require. Some problem do move downstream and that’s good, but the more difficult issues remain unresolved.
I prefer to think of Open XML as a migration path away from Word, and as such I think it’s pretty good. Generally, I’d prefer to move users to a Word-like interface that supports more of their needs than to let them use Word and try to solve what become very difficult problems further downstream. I suppose it varies from site to site, but users are sophisticated enough these days to adjust to a new but familiar WP approach, I think.