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: Why WYSIWYG for XML??? From:"Laurel Hickey" <lhickey -at- 2morrow -dot- bc -dot- ca> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 19 May 2004 11:50:00 -0700
>choose the most lucid authoring
>environment for the process you have chosen. For a monolithic process,
the choice will
>usually be WYSIWCS. For a modular process it will certainly not be
WYSIWCS. It might
>be raw lucid markup, or lucid markup in a structured editor, or a lucid
forms based
>environment.
In this context, WYSIWYG is simply a tool... or feature ...that allows
easier conceptulization of content categories (and modules), allows
easier compiling and sorting of content and easier checking of
structure. There's no reason a good XML app can't give you both... For
HTML, Dreamweaver gives you both! You can even split the view to see
markup and WYSIWYG at the same time. I'd expect nothing less from a
dedicated XML app. I'd also expect it to allow me to switch between
style sheets to facilitate the above however best suited me. It's just
CONTENT. I'm not hurting it!
>WYSIWYG is slightly misnamed. It should be WYSIWCS: What You See Is
What the Customer Sees.
>It means that you are directly handcrafting the final presentation of
the document.
>That means that, apart from physical production, you have a one step
process.
>Everything from composition, to organization, to formatting is done in
one step by one person.
>Taht is precisely what desktop publishing promised.
A WYSIWYG tool like Word has never been used just as a "monolithic tool"
... It's for writing and compiling content that then goes into programs
like Dreamweaver and InDesign, etc. Pity the poor person expected to
send Word files to the printer. (poor, poor, pitiful me!) Have to admit
that "content reclaimation" hit a cord! I think I'll steal that.
-------------------------------------
Laurel Hickey
2morrow writing & document design
lhickey -at- 2morrow -dot- bc -dot- ca http://www.2morrow.bc.ca
SEE THE ALL NEW ROBOHELP X5 IN ACTION: RoboHelp X5 is a giant leap forward
in Help authoring technology, featuring Word 2003 support, Content
Management, Multi-Author support, PDF and XML support and much more! http://www.macromedia.com/go/techwrldemo
>From a single set of Word documents, create online Help and printed
documentation with ComponentOne Doc-To-Help 7 Professional, a new yearly
subscription service offering free updates and upgrades, support, and more. http://www.doctohelp.com
---
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- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
