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.
Re: Flare or Frame as an intermediary for migrating to DITA?
Subject:Re: Flare or Frame as an intermediary for migrating to DITA? From:Robert Lauriston <robert -at- lauriston -dot- com> To:"Janoff, Steven" <Steven -dot- Janoff -at- hologic -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 15 Oct 2014 09:05:26 -0700
I think the basic problem with trying to automate this is that each of
your legacy tags / paragraph and character styles will probably map to
various DITA tags depending on the context, and some DITA tags will be
mapped from more than one legacy tag.
For example, with legacy HTML source, how would you map <p>? With
FrameMaker source, how would you map Body?
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l