Skip to main content
July 30, 2014
Question

My customer got FM 7 and we have FM 11. Can I still edit and save FM 7 files in FM 11? If yes, later, can customer open the edited files in FM 7?

  • July 30, 2014
  • 3 replies
  • 575 views

My customer got FM 7 and we have FM 11. Can I still edit and save FM 7 files in FM 11? If yes, later, can customer open the edited files in FM 7?

    This topic has been closed for replies.

    3 replies

    Bob_Niland
    Community Expert
    Community Expert
    July 30, 2014

    FM11 can open FM7 binary (.book & .fm) files. It may irreversibly convert some content.

    FM11 can save as binary only to FM11 and FM10, but it can also save-as-MIF (to .book.mif & .mif). Any version of FM can open a MIF, but will {mostly} ignore any features from future versions.

    In your case the FM8 (Unicode) boundary might be an issue. Opening FM7 or earlier content in FM8 or later causes some text to be converted from legacy FM roman character codes to UTF-8 Unicode. When saving to MIF, these are not converted back. Just how much of problem this will be depends on how the FM7 authors implemented special characters and any non-Latin characters.

    Also, if you use any other newer features (like Conditional Expressions) not present in FM7, FM7 will ignore those on opening the MIF from FM11.

    Jeff_Coatsworth
    Community Expert
    Community Expert
    July 30, 2014

    Thanks Error – I knew you’d be able to explain the Unicode thing better ;>)

    Bob_Niland
    Community Expert
    Community Expert
    July 30, 2014

    > I knew you’d be able to explain the Unicode thing better ...

    Actually, that's "more than I know about it". In reviewing the history of FM at daube.ch, it appears that Unicode support started creeping in at 7.0, but wasn't really complete until 8.0. I've never seen any detailed description of exactly what newer FMs do in the way of Unicode transformations, and to what, when importing old FM files. I'm not even sure how complete the Unicode support is at FM12, such as support for code points above the BMP (16-bit), and support for notation thereof.

    I work in a shop still using FM7.1 and earlier versions. Some of the legacy content here opens as FM4. When we send out manuals for translation, the translators are almost always on FM8 or later. We bring the content up to 7.1, and send them both binary and MIF*. In current documents, we have implemented all non-ASCII (Basic Latin in Unicode) text as Variables, to provide a central edit point for issues related to the code points used. We ask for translated MIF back, and are fully aware that it might not be useful on our FM7.1 platforms (we also have several FM9, 11 & 12 PCs available in that case).

    ______

    * Why send them MIF?

    Because they might be on an older FM rather than a newer. I rarely deal directly with the translators (our export department is in charge of that), but looking at the PDFinfo of what we get back, some of the houses are astonishingly primitive. In many cases sending them .fm or .mif hardly matters, as they are using Word , often using our PDF as the copy-paste source. We've seen several cases where they apparently used PowerPoint .

    Jeff_Coatsworth
    Community Expert
    Community Expert
    July 30, 2014

    In addition to what Colum said, I think you may also run into the Unicode issue between those 2 versions.

    RoboColum_n_
    Legend
    July 30, 2014

    FM normally allows you to save files in a format acceptable to the previous version using File > Save As. However you have to ensure that there is nothing in the FM11 files that can not be edited in previous versions (e.g. new FM functionality. Maybe the following thread will help. It refers to different version though and FM7 is very old. You will have to save the FM11 files as MIF files and test it out.

    Can Framemaker 12 save files down in Framemaker 11 and 10 ? Is it backward compatible?