Skip to main content
November 10, 2010
Answered

Extraction from FM not copying over correctly

  • November 10, 2010
  • 2 replies
  • 1409 views

Hi, thanks for the help on my other questions!

I am new to FM, was using FM 7.2, but due to the OLE issues, am now using FM9 DEMO under XP. All the documents I am editing were created by the last person who had this position in FM 7.2.

I was asked to provide a table from a chapter of a book to an Engineer who wanted to edit the table. He didn't have FM or the full version of Adobe Acrobat, so my options were limited in how to provide this table to him. I copied and pasted the information into a Word document as formatting wasn't really important - it was the information to edit.

He came back and asked why a row that was not suposed to be included was in the table. When I looked at the FM document it wasn't there, but in the copy and paste had appeared. It is a real row with real information.

I have basically two questions:

1. Why did the information from the table paste incorrectly?

2. If there is a feature in FM to allow more than one version of a document (example: a manual that is all inclusive of information on a product, but only portions of the manual are released to customers) what is this feature called? I want to read about how to use it.

I have a few suspicions as to why this row showed up, but rather than write several likely wrong ideas, I will see what more experienced users have to say.

Thanks

    This topic has been closed for replies.
    Correct answer Van Kurtz

    I would not say that the information is corrupted. As indicated further in Art's post, maybe the row was conditioned and that condition was set to hide in the Frame file. When copied and pasted into Word, the row displayed because Word does not recognize the hidden condition.

    If you DO get into using conditional text in FrameMaker, note that only certain chunks of a table can be conditioned. For example, you can condition an entire row of a table but not just one cell in a row. To understand this, just remember that when the conditioned parts are hidden, the result has to be a complete table. Hiding a row results in a complete table. Hiding one cell does not, because one cannot have a table with a cell cut out of it.

    2 replies

    November 11, 2010

    Erin, one way to really see what's going on in your original FM file would be to save the file as .mif, which is FM's Maker Interchange File format, and then examine the MIF using the freebie MIFBrowse utility, from:

    MIFBrowser

    Although MIFBrowse hasn't been updated recently it works fine with any version of FM.

    If the problem row of the table has distinctive content in it then you can search through the file to find any instance of a string, or you can wade through the MIF syntax to find the table or a perhaps a nearby cell.

    Then you can look at the particular row and all the cells in it, to see if there are any conditions or any other settings applied to the row.

    MIF syntax can be a bit daunting, but it's the only way to see what really is going on with the problem table.

    Oh -- one more possibility for how the problem row might have been hidden, I have seen situations where the text frame on a page was adjusted from the bottom up to be smaller, so that the result was one or more rows of a table were in effect hidden on the page.

    Most of the time when the body page height changes FM will "flow the rows over" to the next page, but I've also seen instances where a conflict between the "keep with next", "keep with previous" settings, plus the table's settings for widow/orphan rows, can result in FM just not being able to display rows as expected.

    Sheila

    November 11, 2010

    Hi Sheila,

    Thank you for the information, I installed the browser and loaded the file with the affected table. I was able to find the string (text) that had been exporting and all I have to do now is pick through and find the reason why it isn't visible. I see all the commands that are used to establish formatting, and it makes sense, I just have to look at it a while to find what I'm looking for.

    This is a very useful tool, like using "Reveal Codes" in Word Perfect a long time ago.

    Thank you!

    Erin

    Inspiring
    November 10, 2010

    To share the table, I would have generated a PDF of the page (or deleted all but the target page from a larger PDF).

    In Acrobat, you can set the options on the PDF to allow editing and cut and paste in Reader, so he could have just copied and pasted into whatever he wanted.

    You could also have saved the page/file/chapter directly to RTF, which he could have opened in Word.

    From the info you provided, no way of telling why the information was corrupted...

    Have you applied all the FM 9 patches, so that when you do Help > About, your version is p255? If not, you should apply them.

    And for your second question, sure; that's what FM's conditional text tools are for. Mark what you want to hide and then hide it... Details on how to set it up are in the Help file.

    Cheers,

    Art

    Van Kurtz
    Van KurtzCorrect answer
    Inspiring
    November 10, 2010

    I would not say that the information is corrupted. As indicated further in Art's post, maybe the row was conditioned and that condition was set to hide in the Frame file. When copied and pasted into Word, the row displayed because Word does not recognize the hidden condition.

    If you DO get into using conditional text in FrameMaker, note that only certain chunks of a table can be conditioned. For example, you can condition an entire row of a table but not just one cell in a row. To understand this, just remember that when the conditioned parts are hidden, the result has to be a complete table. Hiding a row results in a complete table. Hiding one cell does not, because one cannot have a table with a cell cut out of it.

    November 10, 2010

    Hi,

    Thanks for the help, I think this is the reason. I am reading and playing with the conditional text feature in FM9, and have not found the actual condition for this particular row, but I'm not sure what else it could be. It will probably become more clear as I get familiar with the feature.

    Thanks again.