Skip to main content
J
JayHBar
Known Participant
January 27, 2015
Answered

Corrupted Frame files not importing correctly to RoboHelp and can't save MIF as FM

  • January 27, 2015
  • 1 reply
  • 480 views

Hi,

I have Adobe Technical Communication Suite 3.0, which has FrameMaker 10.0.2.249 in it.

I created a user guide in FrameMaker, some of the chapters for which I imported from Word, and little bits of text here and there of which I copied and pasted from Word.

a) When I created a RoboHelp project and imported the Frame files, a little bit of content disappeared. A sentence here, a bulleted item there, not all the content I copied and pasted.

b) I thought I would save the Frame files as .MIF and then reopen them in Frame to get rid of any corruption. They saved as .MIF just fine and they open again with Frame just fine. However, when I try to Save As .FM, I get the message that .MIF cannot be saved as .FM.

I checked the extension in the Save As box and it has no mention of .MIF.

What to do? Any suggestions either for a) or b)?

    This topic has been closed for replies.
    Correct answer Mike Wickham

    This is a bug in the Save As dialog. If the filename is yourfile.FM, you

    can choose MIF as the filetype in the Save as Type box, FrameMaker

    changes the filename to yourfile.mif and saves as mif.

    But, for some reason, if you have a filename of yourfile.MIF and choose

    FM in the Save as Type dialog box, you get that error message and the

    save doesn't happen. The workaround is to delete the MIF extension in

    the filename. Then the save works fine and the file is renamed with an

    FM extension.

    In other words, saving FM to MIF works as expected. FrameMaker renames

    the file extension and saves in the new format. But, in a MIF to FM

    save, FrameMaker refused to rename the MIF extension. (Maybe there is a

    reason for this?) You have to delete the extension or the save won't happen.

    I'm going to report this as a bug.

    Mike Wickham

    1 reply

    M
    Mike WickhamCorrect answer
    Inspiring
    January 27, 2015

    This is a bug in the Save As dialog. If the filename is yourfile.FM, you

    can choose MIF as the filetype in the Save as Type box, FrameMaker

    changes the filename to yourfile.mif and saves as mif.

    But, for some reason, if you have a filename of yourfile.MIF and choose

    FM in the Save as Type dialog box, you get that error message and the

    save doesn't happen. The workaround is to delete the MIF extension in

    the filename. Then the save works fine and the file is renamed with an

    FM extension.

    In other words, saving FM to MIF works as expected. FrameMaker renames

    the file extension and saves in the new format. But, in a MIF to FM

    save, FrameMaker refused to rename the MIF extension. (Maybe there is a

    reason for this?) You have to delete the extension or the save won't happen.

    I'm going to report this as a bug.

    Mike Wickham

    J
    JayHBarAuthor
    Known Participant
    February 2, 2015

    Hi Mike,

    Actually the .mif was not appearing in the Save As box. I had to delete the whole file name and retype it. But it worked. Thanks very much.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices