I just spent a day fixing a problem that shouldn't have happened.
I have a project glossary that was created in Microsoft Word 2007. It consists of definitions for acrnyms and a list of terms which are linked to their definitions in our departmental wiki glossary. The lnking is straightforward HTML to a named anchor in the wiki.
For reasons that aren't important here, we decided tht we needed to convert the glossary from Word 2007 format to FrameMaker (I'm using FM10). I first tried the conversion by File > Import and selecting the Word document format as input source. It didn't work. Links were formatted as hyperlinks (blue underlined text) but none of the links actually worked. Looking at the file, it appeared to have created empty hyperlink markers for each link.
I then tried the conversion using the RTF 1.6 format. This appeared to be more successful - most (but not all) of the terms appeared to having working hyperlinks. However, on checking I found the NONE of the hyperlinks pointed to their intended target. Basically the conversion had inserted hyperlink markers in some more or less random order. As well, markers were inserted in words that weren't hyperlinked.
I ended up using IXGEN's (incredibly useful) expand markers feature to view the markers, and manaully copied and pasted them to where they should have been. I'm just glad there were only about a hundred terms instead of a thousand.
Adobe really needs to put more effort into FrameMaker's import filters. A job that should have taken an hour or two at most ended up taking a day.
I don't know if this is any help for the future, but for converting a
Word document to FM, Adobe recommends using File> Open, rather than
File> Import. In other words, open the Word document directly as a new
document. FrameMaker reads it right in, though I have no experience with
how well it handles Word hyperlinks.
Europe, Middle East and Africa