RE: "MIF"ed Newbie
Steve, I went through a similar exercise recently. It works great if you use the same file names and stay in the same directory. Clint Clint Owen Technical Publications Crane Aerospace & Electronics 425-743-8674 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] om] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 9:01 AM To: framers@lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/clint.owen%40craneae rospace.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. We value your opinion. How may we serve you better? http://www.craneae.com/surveys/satisfaction2006.htm ## Attention: The information contained in this email message may be privileged and is confidential information intended only for the use of the recipient, or any employee or agent responsible to deliver it to the intended recipient. Any unauthorized use, distribution or copying of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately and destroy the original message and all attachments from your electronic files. This email was scanned and cleared by MailMarshal. ## ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
"MIF"ed Newbie
Steve, I went through a similar exercise recently. It works great if you use the same file names and stay in the same directory. Clint Clint Owen Technical Publications Crane Aerospace & Electronics 425-743-8674 -Original Message- From: framers-bounces+clint.owen=craneaerospace@lists.frameusers.com [mailto:framers-bounces+clint.owen=craneaerospace.com at lists.frameusers.c om] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 9:01 AM To: framers at lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh ___ You are currently subscribed to Framers as Clint.Owen at craneaerospace.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/clint.owen%40craneae rospace.com Send administrative questions to lisa at frameusers.com. Visit http://www.frameusers.com/ for more resources and info. We value your opinion. How may we serve you better? http://www.craneae.com/surveys/satisfaction2006.htm ## Attention: The information contained in this email message may be privileged and is confidential information intended only for the use of the recipient, or any employee or agent responsible to deliver it to the intended recipient. Any unauthorized use, distribution or copying of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately and destroy the original message and all attachments from your electronic files. This email was scanned and cleared by MailMarshal. ##
RE: "MIF"ed Newbie
Knowing what I know now, I agree with your assessment. Steve Cavanaugh Sr. Technical Writer NAT Seattle Inc. -Original Message- From: Spreadbury, David [mailto:[EMAIL PROTECTED] Sent: Thursday, October 05, 2006 6:57 PM To: Steve Cavanaugh; framers@lists.frameusers.com Subject: RE: "MIF"ed Newbie Steve, I wouldn't have taken the MIF route to change the fonts. I would have gone through the Paragraph Designer and changed the Paragraph Tags so that they all called Arial instead of Helvetica. Then I would import the Paragraph Tags from the edited chapter to all of the other chapters. This should have accomplished the same thing you did with MIF, only a lot faster and would not have messed up your cross-references. MIF is great for fixing a lot of strange Frame failures, most of which are unknown. The reason this works has never been explained to me, but I use it when nothing else I do fixes the problem. I have used MIF to fix font problems, but never on a global scale. Usually just the Frame file that was displaying the problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] m] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 11:01 AM To: framers@lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: "MIF"ed Newbie
Yes, I was thinking the error I made was a separate directory (if you're under 40, those are called folders I guess...). Thanks for the pointer! Steve Cavanaugh Sr. Technical Writer NAT Seattle Inc. -Original Message- From: Jeremy H. Griffith [mailto:[EMAIL PROTECTED] Sent: Thursday, October 05, 2006 7:52 PM To: framers@frameusers.com Cc: Steve Cavanaugh Subject: Re: "MIF"ed Newbie On Thu, 5 Oct 2006 09:01:22 -0700, "Steve Cavanaugh" <[EMAIL PROTECTED]> wrote: >is there a way to prevent Frame from changing the cross-references when >saving as MIF and then re-saving as .fm? Yes: save the .mif in the *same* dir as the .fm. Otherwise, Frame "corrects" *every* external ref, for xrefs, hyperlinks, graphics, and insets (at least). If you want the .mif to be in a different dir while you work on it, move it using Explorer *after* Frame produces it. That's what we do for the Mif2Go conversion to MIF, which works for individual .fm files or full books, and which we created so that we could put MIF files into CVS conveniently. We don't do that any more, but the MIF destination format choice lives on in Mif2Go, and works fine in the free demo version (which isn't size or time limited): http://www.omsys.com/dcl/download.htm Using that, you can specify any directory you want as the destination, and the files will work correctly when you put them back into the original directory. (Of course, if you open them in Frame in the other dir, they *won't* work. ;-) We generally name the MIF files .fm, so that references from the book file work; when Frame saves them next, it saves them in the real .fm binary format. Makes it easy. Mif2Go also has a "Wash via MIF" command, which saves files (or books) as MIF, then re-opens them and re-saves as .fm. This trip through MIF often cleans up oddities in the Frame files. That works fine in the free demo version too. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. <[EMAIL PROTECTED]> http://www.omsys.com/ ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
"MIF"ed Newbie
Knowing what I know now, I agree with your assessment. Steve Cavanaugh Sr. Technical Writer NAT Seattle Inc. -Original Message- From: Spreadbury, David [mailto:david.spreadb...@tellabs.com] Sent: Thursday, October 05, 2006 6:57 PM To: Steve Cavanaugh; framers at lists.frameusers.com Subject: RE: "MIF"ed Newbie Steve, I wouldn't have taken the MIF route to change the fonts. I would have gone through the Paragraph Designer and changed the Paragraph Tags so that they all called Arial instead of Helvetica. Then I would import the Paragraph Tags from the edited chapter to all of the other chapters. This should have accomplished the same thing you did with MIF, only a lot faster and would not have messed up your cross-references. MIF is great for fixing a lot of strange Frame failures, most of which are unknown. The reason this works has never been explained to me, but I use it when nothing else I do fixes the problem. I have used MIF to fix font problems, but never on a global scale. Usually just the Frame file that was displaying the problem. -Original Message- From: framers-bounces+david.spreadbury=tellabs@lists.frameusers.com [mailto:framers-bounces+david.spreadbury=tellabs.com at lists.frameusers.co m] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 11:01 AM To: framers at lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs
"MIF"ed Newbie
Yes, I was thinking the error I made was a separate directory (if you're under 40, those are called folders I guess...). Thanks for the pointer! Steve Cavanaugh Sr. Technical Writer NAT Seattle Inc. -Original Message- From: Jeremy H. Griffith [mailto:jer...@omsys.com] Sent: Thursday, October 05, 2006 7:52 PM To: framers at frameusers.com Cc: Steve Cavanaugh Subject: Re: "MIF"ed Newbie On Thu, 5 Oct 2006 09:01:22 -0700, "Steve Cavanaugh" wrote: >is there a way to prevent Frame from changing the cross-references when >saving as MIF and then re-saving as .fm? Yes: save the .mif in the *same* dir as the .fm. Otherwise, Frame "corrects" *every* external ref, for xrefs, hyperlinks, graphics, and insets (at least). If you want the .mif to be in a different dir while you work on it, move it using Explorer *after* Frame produces it. That's what we do for the Mif2Go conversion to MIF, which works for individual .fm files or full books, and which we created so that we could put MIF files into CVS conveniently. We don't do that any more, but the MIF destination format choice lives on in Mif2Go, and works fine in the free demo version (which isn't size or time limited): http://www.omsys.com/dcl/download.htm Using that, you can specify any directory you want as the destination, and the files will work correctly when you put them back into the original directory. (Of course, if you open them in Frame in the other dir, they *won't* work. ;-) We generally name the MIF files .fm, so that references from the book file work; when Frame saves them next, it saves them in the real .fm binary format. Makes it easy. Mif2Go also has a "Wash via MIF" command, which saves files (or books) as MIF, then re-opens them and re-saves as .fm. This trip through MIF often cleans up oddities in the Frame files. That works fine in the free demo version too. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
"MIF"ed Newbie
Steve, I wouldn't have taken the MIF route to change the fonts. I would have gone through the Paragraph Designer and changed the Paragraph Tags so that they all called Arial instead of Helvetica. Then I would import the Paragraph Tags from the edited chapter to all of the other chapters. This should have accomplished the same thing you did with MIF, only a lot faster and would not have messed up your cross-references. MIF is great for fixing a lot of strange Frame failures, most of which are unknown. The reason this works has never been explained to me, but I use it when nothing else I do fixes the problem. I have used MIF to fix font problems, but never on a global scale. Usually just the Frame file that was displaying the problem. -Original Message- From: framers-bounces+david.spreadbury=tellabs@lists.frameusers.com [mailto:framers-bounces+david.spreadbury=tellabs.com at lists.frameusers.co m] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 11:01 AM To: framers at lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs
Re: "MIF"ed Newbie
On Thu, 5 Oct 2006 09:01:22 -0700, "Steve Cavanaugh" <[EMAIL PROTECTED]> wrote: >is there a way to prevent Frame from changing the >cross-references when saving as MIF and then >re-saving as .fm? Yes: save the .mif in the *same* dir as the .fm. Otherwise, Frame "corrects" *every* external ref, for xrefs, hyperlinks, graphics, and insets (at least). If you want the .mif to be in a different dir while you work on it, move it using Explorer *after* Frame produces it. That's what we do for the Mif2Go conversion to MIF, which works for individual .fm files or full books, and which we created so that we could put MIF files into CVS conveniently. We don't do that any more, but the MIF destination format choice lives on in Mif2Go, and works fine in the free demo version (which isn't size or time limited): http://www.omsys.com/dcl/download.htm Using that, you can specify any directory you want as the destination, and the files will work correctly when you put them back into the original directory. (Of course, if you open them in Frame in the other dir, they *won't* work. ;-) We generally name the MIF files .fm, so that references from the book file work; when Frame saves them next, it saves them in the real .fm binary format. Makes it easy. Mif2Go also has a "Wash via MIF" command, which saves files (or books) as MIF, then re-opens them and re-saves as .fm. This trip through MIF often cleans up oddities in the Frame files. That works fine in the free demo version too. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. <[EMAIL PROTECTED]> http://www.omsys.com/ ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: "MIF"ed Newbie
Steve, I wouldn't have taken the MIF route to change the fonts. I would have gone through the Paragraph Designer and changed the Paragraph Tags so that they all called Arial instead of Helvetica. Then I would import the Paragraph Tags from the edited chapter to all of the other chapters. This should have accomplished the same thing you did with MIF, only a lot faster and would not have messed up your cross-references. MIF is great for fixing a lot of strange Frame failures, most of which are unknown. The reason this works has never been explained to me, but I use it when nothing else I do fixes the problem. I have used MIF to fix font problems, but never on a global scale. Usually just the Frame file that was displaying the problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] m] On Behalf Of Steve Cavanaugh Sent: Thursday, October 05, 2006 11:01 AM To: framers@lists.frameusers.com Subject: "MIF"ed Newbie I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reproduction, dissemination or distribution of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. Tellabs ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
"MIF"ed Newbie
On Thu, 5 Oct 2006 09:01:22 -0700, "Steve Cavanaugh" wrote: >is there a way to prevent Frame from changing the >cross-references when saving as MIF and then >re-saving as .fm? Yes: save the .mif in the *same* dir as the .fm. Otherwise, Frame "corrects" *every* external ref, for xrefs, hyperlinks, graphics, and insets (at least). If you want the .mif to be in a different dir while you work on it, move it using Explorer *after* Frame produces it. That's what we do for the Mif2Go conversion to MIF, which works for individual .fm files or full books, and which we created so that we could put MIF files into CVS conveniently. We don't do that any more, but the MIF destination format choice lives on in Mif2Go, and works fine in the free demo version (which isn't size or time limited): http://www.omsys.com/dcl/download.htm Using that, you can specify any directory you want as the destination, and the files will work correctly when you put them back into the original directory. (Of course, if you open them in Frame in the other dir, they *won't* work. ;-) We generally name the MIF files .fm, so that references from the book file work; when Frame saves them next, it saves them in the real .fm binary format. Makes it easy. Mif2Go also has a "Wash via MIF" command, which saves files (or books) as MIF, then re-opens them and re-saves as .fm. This trip through MIF often cleans up oddities in the Frame files. That works fine in the free demo version too. HTH! -- Jeremy H. Griffith, at Omni Systems Inc. http://www.omsys.com/
"MIF"ed Newbie
I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
"MIF"ed Newbie
I started using FrameMaker 7.2 fairly recently. I was fortunate to beg a template off an experienced user, saving me many hours of setup for the document I'm writing. I've been reading the list for about six weeks, and numerous times I've seen instructions to save to MIF, do some editing, then read back into Frame. Good, I'm not afraid of that, and looking at a MIF file it seems a great way to get at things. I've been battling fonts here, and after a number of aborted efforts to convert my activities to Helvetica, I decided that Arial would be fine, and after all, it is available on every Windows machine. Anyone can maintain it with Arial. I reasoned that the easiest way to do this would be to save all of the files in my book to MIF and use Search/Replace to get things converted. That way I wouldn't have to go looking under all the rocks in Frame to find all of the Font definitions. So I created a MIF folder and saved the entire book (about 36 files) to MIF format. The Search/Replace went smoothly, and when I read the files back in I was pleased to see the Font change was in place. Good. One thing that I didn't really pay enough attention to though - when I opened the first file, Frame complained about Unresolved Cross-References. Well we see that a lot, don't we. I ignored it for the moment and began adding value to the book. But I kept seeing this on all of the files, so I decided to resolve them yesterday. What I discovered was very upsetting - all of the cross-references embedded on the master pages of each file were now pointing to the MIF folder, which I had sumarily dismissed after finishing with it. All thirty-six files, with about five to seven master pages each, three cross-references per page. OUCH! I just finished about 6 hours of re-establishing all of those cross-references. So, I'm not sure where I went wrong. I had named all of the MIF files as filename.fm.mif which allowed me to easily revert to saving as .fm when I was ready to re-save. If Frame has a habit of doing this kind of thing, I'm not sure I can use MIF again - is there a way to prevent Frame from changing the cross-references when saving as MIF and then re-saving as .fm? Anyone see where I went wrong? Steve Cavanaugh
