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:DocBook and Structured FM 7.1 From:"Joe Malin" <jmalin -at- tuvox -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 19 Oct 2005 17:15:04 -0700
Hi!
I'm starting up a project to use structured FM 7.1 for manuals that will
convert easily into DocBook XML. I want to gain some of the ease-of-use
that structured FM provides, and I also want the option to re-use my
work throughout our company. I'm not thinking of something as formal as
single-sourcing, which is one reason I'm not seriously contemplating
DITA at the moment.
I know the previous paragraph is going to evoke surprise, outrage, and
commentary, and so be it.
Here is my question:
Should I hand-write my own FM EDD that contains elements corresponding
to all the DocBook elements I want to use, or should I make a one-off
DTD that subsets the official DocBook DTD, and then automatically
generate the EDD from the one-off?
I know that XML allows me to *extend* the DocBook DTD, but does it allow
me to *restrict* the DTD as well?
I know that I don't want a FM EDD with every DocBook element in it; that
would be a disaster!
Joe
TuVox, Inc.
-----------------------------------------------------------
19050 Pruneridge Avenue Suite 150, Cupertino, CA 95014-0715
Joe Malin
Technical Writer
(408)625.1623
jmalin -at- tuvox -dot- com
www.tuvox.com
The views expressed in this document are those of the sender, and do not
necessarily reflect those of TuVox, Inc.
Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l
Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005
---
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.