• State Suggested Answer
  • Replies 23 replies
  • Answers 1 answer
  • Subscribers 433 subscribers
  • Views 5478 views
  • Users 0 members are here
Options
Related

Problems with generating target files in MIF 10 format

Bettina Weinmann

For a translation of FrameMaker 10 files from German into Chinese we used the exchange format MIF 10 for Trados Studio. But for 8 of 19 files we cannot generate target files. Studio gave the following error message: 'The index laid outside the area. It cannot be negative or smaller than the list. Parameter name: index' (this is a translation of the German error message).

As workaround I've used the MIF 11 format, translated the files with the TM, but the error message still appears and no target files are generated. Does anybody know how we can get target files?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 in reply to Paul

    Strange indeed. Well, then maybe it's only my installation, but I wonder where's the difference. Another of the Studio mysteries - only this time I'm the one with the mystery, while usually I'm telling others their PCs are guilty. May the antivirus (Norton in my case) be the culprit?

    _________________________________________________________

    When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.

    Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.

  • 0 in reply to Jerzy Czopik

    Reading the thread, I see possible difference - while you tried to save the target immediately after opening the source, Paul did some operations (merged segments, etc.)... which might have changed the internal "SDLXLIFF-in-memory" structure in a way which allowed Paul to save the file.
  • 0 in reply to Evzen Polenka

    Evzen Polenka said:
    Reading the thread, I see possible difference - while you tried to save the target immediately after opening the source, Paul did some operations (merged segments, etc.)... which might have changed the internal "SDLXLIFF-in-memory" structure in a way which allowed Paul to save the file.

    Not in this case.  I used the original MIF files, not the translated SDLXLIFF files.  So I did this:

    1. created a new project in 2021
    2. perfect matched it with the translated SDLXLIFF files
    3. created a TM from the translated SDLXLIFF files when I realised there were too many gaps
    4. pre-translated and then realised the reason for the gaps was almost always don to different segmentation. So I went through the files and merged the segments until I got a TM match

    Then saved the target.  I also tested the MIF files in 2019 and 2021 without translating at all and could repro the problem in 2019, but not in 2021 where the files saved without a problem.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub