Studio 2017:Upper limit of Translation Units(TUs) to be imported into AutoSuggest

I'm sorry. It's me again.

I'm trying to create AutoSuggest (English to Japanese) from my huge master TM (translation units:more than 1,700,000) using Studio 2017.

I heard there should be no upper limit of TUs to be imported from TM into AutoSuggest if there is enough space in its PC to save the AutoSuggest.

But in my case, the maximum TU to be imported into AutoSuggest is set at  531,382 TUs as a default in the AutoSuggest Creating process, though my PC seems to have enough space, that is, 123 GB blank space out of 250 GB for a folder to save the TM and its AutoSuggest. I also tried to create the AutoSuggest from the same TM using my external Hard Disc (900GB blank space out of 2TB). Still failed. Always limited to 351,382 TUs.

What's wrong?

And every time I tried to create the AutoSuggest, it automatically minimized my TM's TU size to 521,382 TUs, 1/3 of the original TM size. I have a master tmx file for this huge TM, so I can create the huge TM again, which has more than 1,700,000 TUs. But unless I find the solution, I can't create the AutoSuggest without minimizing my master TM of the Studio 2017.

Moreover, the created AutoSugget is not displayed on the Edit screen using the minimized TM.

My PC info:

Microsoft Surface Pro 3 (250 GB), CPU: Intel Core i7, RAM:8GB, Windows 8.1 Pro(64 bit), External HD: 2TB, Office 365

PC interface language:Japanese
Language pair: English to Japanese

Nearly all the items are check-marked on the AutoSuggest page <- Option <- File of Studio 2017.

What should I do? What am I missing here? Any suggestion?

Thank you in advance!

Parents Reply
  • Evzen, I think you are right about the fundamental cause. It's probably Translation Memory. I remember when my optimized Trados 2007 TM exported its tmx file to import it to Studio 2017, the Trados 2007 froze for more than 8 hours around the point TU 650,000 and also around TU 1,500,000 respectively while exporting TUs. I'm sure the TUs around 650,000 and 1,500,000 are corrupt or wrong.

    I know from my past experience my legacy Trados 2007 can import this corrupt TUs without decreasing its TU number probably by ignoring the corrupt parts. But I guess the Studio 2017 is too sophisticated to handle the corrupt TUs.

    Is there any way to delete or remove the corrupt/wrong TUs from the tmx file? Do you use Filters?

    Or can I set the Studio 2017 to ignore the corrupt TUs when it's importing tmx files?

    Any advice or info?
    Thank you in advance!
Children
No Data