RE: Moving away from MS Word?

Subject: RE: Moving away from MS Word?
From: "Condo, Candis" <ccondo -at- c-cor -dot- com>
To: "Troy Klukewich" <tklukewich -at- sbcglobal -dot- net>, "SB" <sylvia -dot- braunstein -at- gmail -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 2 Apr 2007 09:46:12 -0700

As was stated at the Writers UA conference last week, we have been
promised a move to XML for 7 years now. Until we get a real tool that
produces real XML, tech writers are not likely to embrace XML.

Candis L. Condo

-----Original Message-----
From: techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf
Of Troy Klukewich
Sent: Monday, April 02, 2007 8:49 AM
To: SB; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Moving away from MS Word?

Re:

<quote>
And then I understand that XML is now the growing trend. How does it
relate to documentation?
</quote>

I have found XML to be the best solution for:

1. Scale
2. Automation
3. Localization
4. Flexibility


I think the most fundamental question facing documentation groups is:
semantic-based content or formatting-based content (or XML versus
desktop publishing)? The vast majority of traditional documentation
systems are format-based, not semantic-based (other than older SGML
systems).

With XML, you move away from formatting altogether and focus on content
semantics, which provides great automation via XSLT to various outputs,
such as HTML and PDF. Need a new output for the latest, greatest help
engine? Design a new XSL transform and leave the content alone.

I've used XML with very large documents 1,500+ pages and large topic
counts 20,000+ with greatly reduced translation costs. The globalization
consultants I've met representing translation interests have all
recommended XML for source content. An increasing number of content
management systems are also geared to XML.

It helps if you have a techie person available to work with output
scripting. Scripting and validation can also provide some sophisticated
error reports to help with authoring along the way.

If I were working for a growing company, I would look into investing in
XML. Most of the conversions I have done involved smaller companies
growing larger, encountering along the way scaling, automation,
localization, and flexibility problems with their legacy content
systems. Most of the conversions I've peformed worked from Word (doc),
RTF, RoboHelp, Frame, and HTML sources. It would be easier and
ultimately much cheaper to build on XML now then re-architect and
convert later.

Most of the big software companies have already moved to XML with more
on the way and a number of scientific industries are standardizing on
XML vocabularies. XML represents a sea-change based on key business
drivers that are not going way, like increased product complexity,
supporting multiple markets or platforms, and globalization.

I also second the suggestion to check out DITA. I highly recommend
checking into DITA at OASIS and IBM as a growing standard for technical
writing. It will get you started on understanding the philosophy and
technical infrastructure, which will help you make an informed decision.

Best of luck.

Troy Klukewich
Senior Manager & Documentation Architect
Documentation & Documentation Services
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats
or
printed documentation. Features include single source authoring, team
authoring,
Web-based technology, and PDF output.
http://www.DocToHelp.com/TechwrlList

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as ccondo -at- c-cor -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit
http://lists.techwr-l.com/mailman/options/techwr-l/ccondo%40c-cor.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output. http://www.DocToHelp.com/TechwrlList

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.


Follow-Ups:

References:
Re: Moving away from MS Word?: From: Troy Klukewich

Previous by Author: RE: Moving away from MS Word?
Next by Author: RE: Happy to be a Tech Writer?
Previous by Thread: Re: Moving away from MS Word?
Next by Thread: Re: Moving away from MS Word?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads