Does anyone have any suggestions on the best way to save approximately 50 FM11 files to .mif version 7 (for translators who only have FM9) ?
I was hoping there was a script or tool to speed up this process, or will we have to save each invidually ?
You can do this with MIF2Go (http://www.mif2go.com/ ) or someone may have some Framescripts/Extendscripts which can do this.
But, are you sure you want to save your files as MIF7? MIF7 is non-Unicode. I guess you may want to save your FM11 files as MIF11, which is Unicode, and you can open MIF11 files with Fm 10, 9 and 8 just fine.
Check with your translators whether they want Unicode (MIF11) or not (MIF7).
No answer on the script, but ...
Why MIF7 ?
This implies to me that FM11 cannot save to MIF9 (as FM9 can). Anyway ...
The way MIF is supposed to work is that earlier FM versions can open later MIF versions, but ignore all tags not implemented.
Your FM9 translators should be able to open MIF9, MIF10 or MIF11 (assuming all of those exist), and would only toss document structuring and formatting tags not implemented.
Perhaps you've already tested the workflow, but my impression is that there are significant hazards in saving down to MIF7 when a document has been authored in FM8 or later, just due to the Unicode issues.
Thank you both - I will confirm with the translator. They were having trouble opening our MIF11 files, I couldn't understand why, they told me they had FM9 - but now I suspect they only have FM7. Argh.
It is just our Chinese translator that does not have the latest FrameMaker. So ... if MIF7 is non-Unicode does that mean we could have issues with the font if they send us a FM7 (MIF) file translated to Chinese and we open in FM11?
This is a problem.
(might explain why they are so cheap).
Yep, if they have only FM7, any Asian characters are going to be in legacy character encodings, and not Unicode.
Not having had to deal with this problem, the encodings might be one or more of those seen at: http://en.wikipedia.org/wiki/Character_encoding
As I understand it, saving Unicode back to MIF7 does not attempt any re-mapping, nor does opening FM7 or MIF7 in FM8 or later. I presume that later versions tolerate (if not support) legacy fonts, but both authoring and receiving systems have to have all the fonts.
I suspect that forum users with direct experience on this can chime in here.
We hire translators, but presently source all our stuff in FM7, with careful attention to non-Roman characters (usually done as vars). So a translation house with FM7 or later is not yet a problem. Once we cross the Unicode border, we'll insist that translators be on a later version of FM. You should too.
Yes, Tina, if you open Chinese MIF7 files in Fm11, you WILL have font issues: you will see a whole bunch of question marks instead of Chinese characters.
Cheap? Yes, if you only consider the price per word. If you take into account the time which is wasted on "project management", "cheap" rates can become very expensive.