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.
| >> What would a 1-page MIF file demonstrate?
| It would demonstrate how easy (or difficult) it is to
| write within the single-source discipline.
Not really. No more than a single Help topic would show how easy it is
to write in a multi-source environment. The picture is bigger than that.
| >> Why does [writing two different text blocks] not count if
| >> you do this a single source environment?
| Because then you're losing the advantage of single-sourcing.
No, you're not. This is the central misunderstanding to which we seem to
keep coming back. I and others have tried our best to convince you that
this viewpoint is not correct, that your understanding of how single
sourcing is actually practiced and what its benefits are is off-base. I
don't think we've succeeded, and I'm beginning to think we won't. So I
will just say, for the benefit of others on the list who may still be
following this overly long thread, that 100% of the organizations I am
familiar with that use the single source approach do in fact write a
limited number of output-specific text blocks and do nonetheless derive
the advantages of single sourcing.
| >> Why would you try to [thread together pedagogical material,
| >> and reference material into a single block]? Pedagogical,
| >> reference material often go in separate documents, never mind about
| >> separate text blocks. I don't see a connection to single sourcing
| Because I'm trying to save effort; isn't that the idea?
I do not think you will ever succeed in saving effort by attempting to
combine pedagogical, procedural, and reference material in a single text
block. If you believe that the combination of such disparate content
within a single paragraph is a goal of single sourcing, again I think
you have a basic misunderstanding.
| Digital effort began with the merger of the training and
| writing groups. Both sides agreed there was tremendous
| overlap of information; what they never agreed on was a
| unified presentation. Even if the sides had agreed, the
| approach to tag definition would have doomed their best efforts.
Ah, Digital, one of my first employers. Why didn't you say so? Now I can
just imagine this project in all its, well, Digital-ness. ;-) I imagine
it was destined to fail from its inception; the belief that pedagogical
content from an instructional group and technical content from a
documentation group can be easily combined is, in most environments,
unrealistic. That is not a failure of the single sourcing methodology or
of any particular set of tools. If you sit down with a fork and knife
and attempt to eat a bowl of cement, well, it won't go very well; but
that doesn't mean eating is a bad idea.
Consulting & Training on FrameMaker & WebWorks Publisher
Consulting & Training on RoboHelp
WebWorks Publisher Certified
Member, JavaHelp 2.0 Expert Group
Moderator, HATT & wwp-users
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.