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.
In 2008 I did a huge project where we converted a ton of Frame 7 files
to Word through Mif2Go. Jeremy Griffiths, the creator, is a really
good resource if you get stuck. I don't know why you think you have to
export one .fm at a time. I found Mif2Go to be light years faster at
converting entire books than Frame's built in RTF export function. Are
you sure you have Mif2Go installed correctly?
The first thing you have to remember is that because Mif2Go is meant
for one-way conversion (purely to provide reviewers with a Word
document for revisions and commenting), all numbered lists are hard
coded. This solved the initial problem, but creates additional work
for those who want to continue their maintenance in Word.
Fortunately for us, our Frame template and our Word template were
closely matched, because our team maintained documentation in both
formats depending on the needs of the particular division. Even still,
I spent a lot of time practicing with style mapping before converting
documents, and had to draw the line on nailing down every single style
on the list.
So, my recommended tips (based on 2 year old memory):
1) Make sure Mif2Go is installed correctly. You should see a File >
Mif2Go menu option.
2) Set your Word template up with standard styles, and make it look
like your Frame template.
3) Map your styles in the configuration file. This is dependent on the
different output settings, and I can't remember which one I used. All
I remember is Heading 1 is Heading1 (nospace, aligned with Word's
internal VBA constants: )
4) You need to uninstall and reinstall when you switch from the demo
to the paid version. For some reason the old driver that inserted
Jabberwocky text remained resident. I'd probably reboot between
uninstalling and reinstalling to ensure the file can be overwritten.
5) Even though with proper mapping, the layout will look the same, you
will want to hand format the text using keyboard shortcuts after the
initial conversion. I set up a secondary template with keyboard
shortcuts mapped to the styles and loaded it into my Startup folder.
This way I could use the same keyboard shortcuts in every document.
--
Tony Chung: Creative Communications
Cell: +1-604-710-5164
Email: tonyc -at- tonychung -dot- ca * Web: http://tonychung.ca
Skype: tonychung.ca * GTalk/MSN: tonychung -dot- ca -at- gmail -dot- com
Twitter: @techcom * Facebook: http://www.facebook.com/tonychung.ca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
