Skip to main content
Known Participant
November 9, 2010
Answered

Extremely big MIF file size!

  • November 9, 2010
  • 1 reply
  • 1124 views

Hello

I'm working on a .fm file. The size of this file is 3.738 KB. It's composed by 73 A4 pages with tables, text and referenced images.

When I'm trying to save as mif, it generates a 44,1 MB .mif file.

Initially was an external work, and the designer embebed the images. Later, I repaired all images to change them into referenced files.

Could it be the problem? I don't know what to do. I need to separate  .fm files for having <5 MB MIF files. A 44 MB file is a giant file!!!!!

Thanks.

    This topic has been closed for replies.
    Correct answer Michael_Müller-Hillebrand

    Raul,

    MIF files are usually a lot larger then their binary FM counterparts, a factor of 10 is no surprise to me.

    Why would you need files below 5 MByte? You can easily ZIP them down to that size, I would guess.

    - Michael

    1 reply

    Michael_Müller-Hillebrand
    Legend
    November 9, 2010

    Raul,

    MIF files are usually a lot larger then their binary FM counterparts, a factor of 10 is no surprise to me.

    Why would you need files below 5 MByte? You can easily ZIP them down to that size, I would guess.

    - Michael

    RaulM21Author
    Known Participant
    November 9, 2010

    I must send mif files to other people who works over across. They told me not to send files higher than 5 MB for the Across translation. I don't know exactly why, just follow orders. They didn't reply my questions.

    Thank you

    Stefan_Gentz__tracom_de_
    Participating Frequently
    November 9, 2010

    Raul, if the MIF file get's that big, it is likely that there are still some embedded images (remember to also check reference and master pages). In FM 9 it's very easy to check for embedded images via > View > Pods > Insets. If an inset shows "No File" instead of a Path, it's an embedded one.

    Regarding across: indeed there are quite some problems with bigger files especially if you work with across Language Servers involving distributed locations over the web. Generally speaking, across is quite slow in everything, but especially in reading and analyzing big files. I did not have to process a 44 MB MIF file in across yet, but it might take  anything from minutes to hours depending on server power and distribution scenario. That's probably why "they" don't want big files. I suggest to do your best to reduce files by checking again for embedded insets. Also it might be a good idea to process the files in SDL Trados alternatively as SDL Trados has no problems with big MIF files. I have processed MIF files of several hundred MB with tons of embedded graphics in SDL Trados without any problems.

    Cheers,

    Stefan Gentz