[Date Prev][Date Next] [Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]

backpedaling MIF files RE: fmbatch to convert to FM6 (or 5.5.6?)



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. For those of us who backpedal FM7 and FM6 files to FM5.5.6 via MIF there is always the worry that some real data might be lost in this manner, even though we are working in a FM5.5.6 created template. A Perl script that did this would be useful to many of us.

Here's one of the spurious errors that we don't care about since we will be using the file in a FM5.5.6 context:

maker: MIF: "filename" (1779): Invalid opcode: PgfPDFStructureLevel.
maker: --- Skipping these chars:
maker: 3 >
maker: ---------- Done skipping.

Similarly structured 4 line errors occur for these opcodes:

maker: MIF: "filename" (2513): Invalid opcode: ContPageNum.
maker: MIF: "filename" (2514): Invalid opcode: PgfNumbering.
maker: MIF: "filename" (2515): Invalid opcode: VolNumComputeMethod.
maker: MIF: "filename" (2516): Invalid opcode: VolumeNumStart.
maker: MIF: "filename" (2517): Invalid opcode: VolumeNumStyle.
maker: MIF: "filename" (2518): Invalid opcode: VolumeNumText.
maker: MIF: "filename" (2519): Invalid opcode: ChapterNumComputeMethod.
maker: MIF: "filename" (2520): Invalid opcode: ChapterNumStart.

Does anyone have a comprehensive list of these opcodes not available in FM5.5.6? Anybody want to bite off constructing a script to remove this log noise for purposeful backpedalers of MIF files? This is something I've had in mind for quite a while, but I never seem to find the time. (How's that for off-loading a task?)

Thanks.

Craig
Los Jugadores Bazutadores
-----Original Message-----
From: Rick Quatro [mailto:rick@frameexpert.com]
Sent: Thursday, March 27, 2003 10:28 AM
To: Framers List
Subject: Re: fmbatch to convert to FM6


Jennifer,

To answer your second question: these errors are normal because the FM6 MIF
parser does not recognize the FM7 information in the file. The MIF parser is
designed to be "forward compatible" so it can open MIF files created with
later versions of FrameMaker. It writes the unrecognized commands to the
Console.

Rick Quatro
xxxxxxxxxxxxxxxxxxxxxxxx


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **