Saving Frame 10 files in batch to Frame 7

[de Rouck, Tom (Gent)]

Hi Frank,
Thanks for your reply.
In the MIF the tags "<u\><c\>" are wrongly added, leading to a path "..\xxxx.fm".
The "..\" is wrong, so if I delete the "<u\><c\>" tags in the MIF via a text editor my path is correct. But that's something I don't want to do manually for all 200 files, obviously. Maybe I should find out how I can find and replace some code in a batch of MIF files (via text editor)? There should be freeware for that, right?

Regards,

Tom De Rouck
SGS Documentation Services
Junior Project Manager
Phone:  +32 (0)9 242 81 77

From: Frank Elmore [mailto:frank at elmsoftonline.com]
Sent: woensdag 27 juni 2012 19:11
To: de Rouck, Tom (Gent); framers at lists.frameusers.com
Subject: RE: Saving Frame 10 files in batch to Frame 7

I'm not sure if this is a bug in Fm10 or if that is the way it is designed to work. XRefAltText, XRefClientName, XRefClientType and XRefSrcElemNoUniqueId are all properties that were added to FM in version 9. However, when I used Fm10 to save an Fm10 document as Mif 7.0, the mif file contains these invalid properties. This explains why you are getting those messages when opening the Mif7 document generated by Fm10.  I tried this myself using the FM10 UI (not FrameScript) and I get the same results.

As far as the bad links are concerned, are the files in the same relative position? You might have to open a mif file using a text editor and look at the <XRefSrcFile property of the <XRef to see where Fm7 thinks the file to file link should be.

Frank Elmore
ElmSoft, Inc.
FrameScript and EPubFm

From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at lists.frameusers.com> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of de Rouck, Tom (Gent)
Sent: Wednesday, June 27, 2012 8:13 AM
To: framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
Subject: Saving Frame 10 files in batch to Frame 7

Dear Framers,

Framemaker 10 + Framemaker 7.2 + Framescript 5.2R1p248

Am I correct that for saving Framemaker 10 files to Framemaker 7, in batch, I need to pass by MIF7, right?

In Framemaker 10, I have a script that saves all my Framemaker 10 files from a book to MIF7.
In Framemaker 7.2, I then use another script to save a folder of MIFs to FM7. I then get a lot of opcode errors in the console:

(13362): Invalid opcode: XRefSrcElemNonUniqueId.
--- Skipping these characters:> ---------- Done skipping.MIF: "C:\temp\xxx.mif" (13363): Invalid opcode: XRefAltText.
--- Skipping these characters:> ---------- Done skipping.MIF: "C:\temp\xxx.mif" (13364): Invalid opcode: XRefApiClient.
--- Skipping these characters:< XRefClientName > < XRefClientType > > ---------- Done skipping.MIF: "C:\temp\xxx.mif"

The files then open with Framemaker 7 but links between different documents of the same book do not work any more.

Can someone help?

Thanks in advance,
Tom

Tom De Rouck
SGS Documentation Services
Junior Project Manager

SGS Belgium NV
Derbystraat 243
B-9051 - Gent
E-mail :   tom.derouck at sgs.com<mailto:tom.derouck at sgs.com>

Information in this email and any attachments is confidential and intended solely for the use of the individual(s) to whom it is addressed or otherwise directed. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. Finally, the recipient should check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. All SGS services are rendered in accordance with the applicable SGS conditions of service available on request and accessible at http://www.sgs.com/en/Terms-and-Conditions.aspx

Information in this email and any attachments is confidential and
intended solely for the use of the individual(s) to whom it is addressed
or otherwise directed. Please note that any views or opinions presented
in this email are solely those of the author and do not necessarily
represent those of the Company.
Finally, the recipient should check this email and any attachments for
the presence of viruses. The Company accepts no liability for any damage
caused by any virus transmitted by this email.
All SGS services are rendered in accordance with the applicable SGS
conditions of service available on request and accessible at
http://www.sgs.com/en/Terms-and-Conditions.aspx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20120628/f186766e/attachment.htm>