Windows 7 64-bit. Framemaker 11, Build 126.96.36.1992
I have two files in a book (out of 5) that always ask if I want to save changes - even when I've made none.
I have checked this repeatedly... just open the file and then immediately close without touching the document. The other three files (with very little content right now) do not exhibit this behavior.
What might cause this?
I've seen this posting, but for me... it's not every file.
Mar 28, 2012 10:58 AM in reply to Terri in Wis Rapids
Since its happening with every file, my suspicion is that your application data is corrupted. Try this:
I'm betting you have alerts (fonts, xrefs, etc) suppressed via the Prefs. Thing are substituting upon open, but you're not seeing the messages.
Also, FM keeps track of many things (text symbols, rulers, etc.) that you likely don't consider "changes" to your document. Changing those setting results in the same mssg upon close.
FM maybe updating cross-references, text insets, system variables (some are time-stamped with the last file open) or other items behind the scenes activities, so the document gets flagged as "dirty". FM is just asking if you want to save it with this revised information.
A usual suspect:
If you are using variable Current Date (Long or Short) anywhere in the document, such as headers/footers, then the document is in fact being changed every time you open it, and causes this behavior. Changing it to Modification Date fixes that ...
... but can result in book components having different dates if you regenerate the output without doing an Update Book. We've opted to use Current Date in our footers, and put up with the nuisance Unsaved Changes.
Ding! Ding! Ding!
Thanks, Matt. That was it. I inserted these "special characters" from WingDings using the Windows Character utility. I noticed (after that) the "font substitution" message appearing from that point on telling me that "MS Shell Dlg 2" font is not available. I found it was pointing to these new symbols (the only thing that could cause the font message), but I couldn't figure out how to get rid of it, so I supressed the message.
Any ideas how to get rid of that message? I suppose I could get rid of the symbols and use a custom circle-with-a-number-in-it graphic in its place.
As any harmonium-loving copyist could tell you … circled numbers are available in (many) Unicode fonts, starting at with ① at U+2460. I too had problems with MS Shell Dlg before I worked out how to use the character pallette. N
Deleting the C:\Users\[user]\AppData\Roaming\Adobe\FrameMaker\ directory solved my problem. Our company uses a mirrored network dirve for our My Documents folder and the latency involved in this seems to cause many different problems. One of which is system instability and corrupted files.
This simple solution may not permanently solve my issue, but it does fix it, so that the FM files are no longer identified as MIF when they aren't.