[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Ede, Craig" <craig.ede@xxxxxxxxxxxxx>
Subject: Re: backpedaling MIF files RE: fmbatch to convert to FM6 (or 5.5.6?)
From: "Thomas Michanek" <thomas.michanek@xxxxxxxxx>
Date: Thu, 27 Mar 2003 18:59:25 +0100
Cc: <framers@xxxxxxxxx>, "Boyce, Daniel" <dan.boyce@xxxxxxxxxxxxx>
References: <LISTMANAGER-71113-15385-2003.03.27-10.14.55--chattare#telia.com@lists.FrameUsers.com>
Sender: owner-framers@xxxxxxxxx
> Wouldn't it be nice to have a tool that scans a log of these MIF error > messages and throws away all the spurious ones and keeps only those > that would indicate meaningful (unintended) use of an FM6 (or FM7) > feature or actual loss of content. That's not entirely easy, in the general case, as a single MIF statement doesn't give you context enough to know what effect ignoring the statement will have. > Does anyone have a comprehensive list of these opcodes not available > in FM5.5.6? It's in the online MIF manual, the chapter "MIF compatibility". > Anybody want to bite off constructing a script to remove this log noise > for purposeful backpedalers of MIF files? I can make a simple UNIX shell script, provided you decide what is noise and what is not. It's not entirely easy to know whether you actually use the new <$chapnum> variable for anything useful in your FM7 files, even though it's always there in the MIF file. Then you'd have to analyze the context of the statements, which is a little bit trickier than a simple "grep" or "sed"... - - - - - - - - - - - - - - - - - - - - - - Thomas Michanek, FrameMaker/UNIX/MIF expert Technical Communicator, Uppsala, Sweden mailto:Thomas.Michanek@telia.com http://go.to/framers/ - - - - - - - - - - - - - - - - - - - - - - ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **