In regards to FrameMaker, are there any known document issues going from an older version like 7 or 8 to 2015/2017?

[karenj3842416]

In regards to FrameMaker, are there any known document issues going from an older version like 7 or 8 to 2015/2017?

I have a few documents that someone else created in Verson 7.  Company is purchasing version 2017.  I'm afraid that the new version of FrameMaker will not work with the old version.

Also, I'm inheriting a few documents from our outside contractor created that used FrameMaker 8 to crea

[Jeff_Coatsworth]

Unicode fonts would be the major thing you might run into - always maintain a starting point backup & maybe save off as MIF in the earlier versions as an extra layer of backup

[Bob_Niland]

Is the FM7 still operational? And what platform is it on (Mac, Unix, Windows)? There might be platform issues.

When jumping forward multiple releases, it's always a safe idea to do a MIF wash first, or even do the migration via MIF. Since that's not built-in on FM7, it means save as MIF on 7, re-opening, and saving again.

The Unicode thing is unobvious (and will already have been confronted if moving from FM8). Only some of the pre-8 content is converted from Frame Roman to UTF-8. Not having investigated it deeply, my guess is that it's limited to Frame "Standard" characters that have code points above U+00FF now. Anything to which a character format or local override had been applied, using a non-Roman font, may not be converted.

The legacy font you were using on FM7/8 might not have populated anything above that, which could result in "?" representations, or substitutions from other fonts, or even Windows faking it for you.

More info here, or not.