Downgraded Framemaker

4 replies
651 views
Translate

I recently upgraded to 64-bit Framemaker 2019 from 32-bit Framemaker 2017 and converted my existing files. Unfortunately, the new Framemaker won't talk to 32-bit ePublisher Webworks. Webworks does not currently have a 64-bit version (supposedly it is coming out in July), so I downgraded back to 32-bit Framemaker 2017, but now I can't open my files. Is there a work around or some way to convert my files back to something that can be opened with 2017?

This topic is closed to new replies. Start a new post to keep the conversation going.

T

TomPedersenAuthor

Participant

Thanks so much for the info.

Translate

Bob_Niland

Community Expert

There's also "heroic open" in earlier releases, but it's a last resort.

If the latest FM is available, save back as prior release .fm, or save as .mif.

Whenever a mixed-release environment lurks (such as sending out for translation), stewardship needs to routinely include saving as both .fm and .mif.

Translate

frameexpert

Community Expert

You have to open the files in FrameMaker 2019 and save them down to 2017. You can only save down one version (32-bit versus 64-bit doesn't matter). If you have a lot of files to save down, check out my ConvertDocs script at frameexpert dot com.

Translate

www.frameexpert.com

Jeff_Coatsworth

Community Expert

I wasn't aware that there was any difference in the .fm files produced, but you could install the 64-bit on another machine, open the files and save as MIF to be able to transfer them back to the 32-bit version.

[EDIT - I missed the "I'm going back to FM2017" bit when I answered. There's no difference in 32/64-bit FM2019 files. Personally, I'd just use the 32 bit version of FM2019 instead of going back to FM2017]

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.