FrameMaker 8: Save As MIF 7.0 as default

Forum|Forum|7 years ago
January 30, 2019
2 replies
1209 views

I'm using good OLD dzbatcher to automate FrameMaker book builds. Part of the build requires that I save a FrameMaker 8 FM file to MIF 7.0.

FrameMaker 8 provides two save-as MIF options: MIF 8.0 and MIF 7.0, where MIF 8.0 is the default.

Does anyone know how to make MIF 7.0 the save-as default? Failing that, how to remove the MIF 8.0 save-as option which I don't need).

framemaker save-as

This topic has been closed for replies.

Matt-Tech Comm Tools

Community Expert

Your question is about MIF standards, but your problem seems to be with XML export.

Is there a reason you're using MIF to somehow produce your XML?

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant

LinSims

Community Expert

I can't help you with your question, I'm afraid, but I am curious. Why do you want to save to MIF 7 if you're using FM 8? As I recall, one of the things that was new in FM 8 was the addition of unicode support, and I think you lose that if you save backwards.

G

gordonf44886270Author

Participating Frequently

Welcome to the rabbit hole......

Without going into brain-tumor-inducing detail, I'll just say that we have a very old propriety documentation build and delivery system. The XML generated from FM 8 and later versions contains a "bug" that Adobe refuses to address. The last "clean" XML produced by a version of FrameMaker was FM 7.

So we have to downgrade to FM 7 in order to produce usable XML. However, MIF 8.0 contains unicode characters that don't translate well in FM 7 and the resulting XML.

S

Stefan Gentz

Community Manager

Hi gordonf44886270 ,

The XML generated from FM 8 and later versions contains a "bug" that Adobe refuses to address. The last "clean" XML produced by a version of FrameMaker was FM 7.

That's a surprising statement in many ways, but especially considering the large number of companies worldwide working very successfully with FrameMaker and XML.

Could you please let me know which bug that could be? I would love to look at it and check if it is actually still present in one of the newer versions. Also, I'd like to know who at Adobe has told you that we would "refuse" to address this bug, whatever this bug might be.

Kind regards,

Stefan Gentz
Worldwide Technical Communication Evangelist

Connect with us:

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded