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.
Subject:Re: Giving up on XML From:Stuart Burnfield <slb -at- westnet -dot- com -dot- au> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 21 Mar 2007 11:03:54 +0900
Another benefit of structure is that it's easier to get new value from
old manuals.
To give one example, IBM is implementing a clever advanced search
capability across a library of several hundred old books. These books
are maintained by different groups around the world using different
editors, but because the source files are SGML the tags are structured
in a predictable order. This means that the people responsible for the
search project could say to the doc groups, "For each instance of X
insert a tag in this format between the </Y> and <Z> tags."
For the books that I looked after (4,500 pages), the changes took a
morning to implement, most of which was thinking, experimenting and
checking. The actual find/replace took about ten minutes. If the books
had been unstructured I doubt the project would ever have started--it
would have been just too much work.
These benefits obviously accrue mainly to large companies with big
libraries of documentation, but it would be shortsighted to say that XML
is therefore only for the IBMs and Suns of the world. The idea is to
reduce the cost of entry so that the benefits are available to smaller
outfits.
Stuart
________________________________
Janice said:
We used to use FrameMaker and constantly were telling
writers that they needed to use the catalogs for formatting
and not apply bold or italic through the menus. Guess what?
When it came time to convert the documents to SGML,
some of the formatting in some documents vanished
because the writers had used the menus.
I'd rather have structure imposed from the beginning for
the sake of consistency and clearer documentation for our
readers. Getting the writers to incorporate editing markup
of the text itself is challenge enough. Having inescapable
structure rules means one fewer thing that will be inconsistent.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-