TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
To summarize, you want
* easy customization
* easy translation
* multiple output formats for the same information
You implement reuse with a variety of approaches, but the key one is
management buy-in. Having your head of tech pubs say it's a "good idea"
is not sufficient.
I think that easy customization demands content management more than
XML. Of course, since XML is a text format, you can do content
management much more easily than with .fm files!
XML lends itself to easy translation. I've seen "translation" mentioned
as one of the main arguments for using XML. I happen to have a
background in internationalization and localization, so I agree!
Multiple output forms for the same information is easy to do with XML,
but XML is not the only source format that can do it. Also, multiple
output formats don't "magically" come when you use XML.
jmalin -at- tuvox -dot- com
The views expressed in this document are those of the sender, and do not
necessarily reflect those of TuVox, Inc.
From: devdra darke [mailto:devdra -at- sympatico -dot- ca]
Sent: Tuesday, August 09, 2005 1:44 PM
To: Joe Malin; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: xml tool questions
Thank you for the information. I would never have thought of
Dreamweaver, but I will certainly take a look at it, as well as XMetal,
XMLSpy and Arbortext.
I appreciate that you took the time to mention schemas and transformers.
I suppose this is why I keep hearing about 'DITA' as a possible choice
for technical writers using XML.
The problems I am trying to solve are:
* a lot of reusable content that is not being reused and has become
* a lot of custom guides and help files desired as our cilents tend to
pick and choose modules in our application
* a lot of custom information as our clients often received information
tweaked for their specific instance of our software
* simplified translation
* simplified single sourcing of pdf and help materials as well as
editable source material for internal clients.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.