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.
'The most commonly-stated reasons for adopting
structured documentation techniques include:
Automation, Reuse, Single-sourcing, Productivity gains
(resulting from the above)'
"However, none of these (or other) advantages require
structuring at all. Non-SGML markup languages such as
troff or TeX, and even help-authoring tools like
RoboHelp, all allow automation, reuse, and
Chris, I do have one small question:
*Why is it* that you don't regard tagged text as being *structured*?
Although TeX was designed as a typesetting language, TeX applications
actually do impose tags for content elements, to give but one example.
There is nothing, so far as I am aware, that says that "structured"
Perhaps you know something of which I am unaware?
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 & 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 & Manual: http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-