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.
Opinions and counter-opinions do not consitute war, Bill. Most
proponents of XML formatted docs are happy just to apply a standard, any
standard. Each schema has its advantages, disadvantages and well honed
workarounds. So, I'm not opposed to DocBook. I simply reiterate with
support from your posting that...
>I find however that [DocBook] may require more massaging than DITA does
for single sourcing. Docbook has been good to those who use it and is
certainly better supported than DITA.
"The finest language is mostly made up of simple unimposing words."
From: Bill Lawrence
Sent: Wednesday, August 17, 2005 10:14 AM
>In DocBook's case, you physically encapsulate your information in
>chapters, articles, etc in the following order. After you have decided
>whether you're writing an <article>..or..wait..maybe it's a
><chapter>...then you proceed to create the meat of the information.
>Finally you hope that the structure you started with suffices for your
>project. IMHBOMO, Docbook's great if you've got a publishing deal with
>SAMS. I find however that it may require more massaging than DITA does
>for single sourcing. Docbook has been good to those who use it and is
>certainly better supported than DITA.
Not to engage in religious wars over DTDs, but there are better ways to
approach single source design in Docbook. We write all our single
source modules (files) as Docbook sections. Sections can nest within
sections, which makes them extremely flexible. We get some DITA-like
functionality by using attributes to identify information types for the
modules, and we can conditionalize on those information types.
The hierarchical structure, such as chapter or article, isn't a problem
'cause we create documents or help through "driver" files that reference
the modules via xinclude elements. The driver files are kinda like
"master documents" in Word. Only the driver files contain the
hierarchical elements. So, a shorter document that uses article as the
root can reference some of the same information modules (sections) as a
longer document that uses book as its root.
(This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.
Ce courriel est confidentiel et protege. L'expediteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) designe(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immediatement, par retour de courriel ou par un autre moyen. )
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.