FrameMaker compatibility issues

[Omni -29522302f2za]

Why FrameMaker 17.0.0.226 docs are not opening in the older version of the FrameMaker?

[Jeff_Coatsworth]

Did you "Save As" that target version or as MIF?

[Omni -29522302f2za]

No, I didn't save it as MIF.

[Omni -29522302f2za]

Is FM 2022 version backward compatible with FM 2019?

[Barb Binder]

Hi @Omni -29522302f2za:

No. (Well, not directly.)

FrameMaker documents can always be opened version it was created in, and later. For example, a Fm 15 file can be opened by 15, 16 and 17.

If you want to open a file in an earlier version, you will need to save it as .mif (maker interchange format). For example, a Fm 17 file needs to be saved as .mif to be opened in Fm 15 and 16. 

For this reason, it's best for all participants to be on the same version. 

~Barb

[Bob_Niland]

Barb: For this reason, it's best for all participants to be on the same version.

But even if they are, always re-save to MIF when wrapping up a project. You never know what the next contractor or translator will be running.

[Barb Binder]

Bob, I have lost track of the number of the best practices I have learned from you. 

~Barb

[Jeff_Coatsworth]

Some versions had a "Save As" version available as the one previous (I guess for mixed environments where not all users were on the same version), but I'm not sure what options FM2022 has.

[Winfried Reng]

FrameMaker 2022 can save back as FM 2020 files.

When you want to save as in even older versions, then you would need one of the Rick's scripts.

Or from Klaus Göbel this free script:

https://4xscripts.com/scripts/free-scripts.html#4X_SaveDocAsOldFMVersion

[Bob_Niland]

re: Some versions had a "Save As" version available as the one previous (I guess for mixed environments where not all users were on the same version),…

My recollection, back to FM3, is that FMₙ can save-back as .fm & .book binaries to FMₙ₋₁

re: …but I'm not sure what options FM2022 has.

My recollection from the 22βeta was the same. My copy of '22 isn't running at the moment.

My recollection?
Yeah, I never really used the feature, whereas Save-as-MIF was routine practice. However, avoid any temptation to save as MIF7, except in seriously unlikely scenarios, where you are prepared to deal with what is apt to be widespread ?codepoint debris.