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.
I'm not a Framemaker or XML expert, so I have dumb question: why move to
Framemaker, which uses SGML? I make no pretension to understanding the
differences between XML and SGML. I guess the reason I'm curious is that
I'm documenting applications written in VB and XML, and wondered if there
would be an advantage to moving to authoring tools other than Word and
Robohelp html now, or if I should consider it for future product releases.
Thanks in advance for any insight you can provide.
Connie Giordano
-----Original Message-----
To Andy and Other TWers:
I've seen faint glimpses on this list about developing documents in XML.
From what I've read on some code development sites, XML may replace RTF,
making early adherence to this standard a bonus for document groups. We're
been so convinced of this that we've switched to FrameMaker and are
migrating our document database to one that supports XML.
Who else out there is moving a documentation group to the XML standard, and
how are those folks making the migration from supporting RTF to XML? Anyone
banging their head against their keyboards yet?
Love to see a dialog on this one.
Thanks.
Ed Klopfenstein
**********************************
Ed Klopfenstein
Senior Technical Writer
Accu-Fab Systems, Inc.
