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: migrating from Framemaker to XML/XSLT From:"Darren Barefoot" <darren -dot- barefoot -at- capeclear -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 28 Mar 2002 16:39:40 -0000
The only advice I can offer is: Develop your patience. I applaud your
early-adoptive strategy, and definitely think this is a wise solution to
your particular problem, but, in a word, yowza. I hope you've either got
some technically-savvy writers or some sympathetic developers kicking
around. Given the relatively new state of XML/XSLT tools (and in
particular, those for the doc-writing types), this won't be easy and
will require a whole heck of a lot of patience and, I expect,
considerable kludging.
That said, it'd be really cool to have all of your docs in XML files
that you could instantly deliver in many forms to many people, thanks to
XSLT and the like.
I haven't tried this, but one of our products is an XSLT-generator.
Basically, you map XML schemas to other schemas (or SOAP messages or
DTDs or whatever) and generate XSLT, which you can then deploy to
transform XML documents. This might not be of much use for you guys
(it's more for EAI and Web Services and the like), but while documenting
it I did learn how fussy XSLT and its gloomy cousin Xpath is. Thanks.
DB.
Zack Brown (whose name sounds like a secret identity) wrote...
> Another is that it is possible to perform
> transformations on XML using a combination of scripts and
> XSLT, that could be very useful, but that would be difficult
> under more all-in-one solutions.
>
> I'm not trying to start a religious war about what is better.
> Framemaker is an excellent tool and we will still use it for
> a large portion of our documentation. My question is, has
> anyone else attempted a migration to XML/XSLT, and what
> advice can they offer?
>
> Thanks,
> Zack
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PC Magazine gives RoboHelp Office 2002 five stars - a perfect score!
"The ultimate developer's tool for designing help systems. A product
no professional help designer should be without." Check out RoboHelp at http://www.ehelp.com/techwr
---
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.
