Stefan Gentz wrote:
I can only recommend to update to TMW 188.8.131.528. TRADOS has fixed a lot of problems especially when it is about Unicode and code page handling (e.g. now you can read Russian characters in the edit segement dialog, if you are running TMW on a german windows).
This may be very helpful for us because we had some problems with Russian and East European languages as source languages.
I hope that TRADOS gave you the good advice to add meta data (fields) to your TM and add TUs with project filter settigs.
We came up with this idea on our own. However, we make extensive use of meta data. Otherwise it would be impossible to manage our TMs.
1) Do your TMs have "Allow multiple translations for identical source segments" activated? I faced some problems with big TMs and virtually nonsens matches with TMs with some hundred thousand TUs.
Yes, we allow multiple 100% matches. I can imagnie that this also has an impact on our memories.
2) Do you have single language pair TMs? Or do you have TMs with more than one target language? This also seems to cause some trouble with big TMs.
We only use single language pair TMs. Anything else is much too dangerous. If a TM gets damaged you risk loosing translations in more than one language. In addition exclusive access for maintenance blocks more than one translation team.
3) Did you try to
a) reorganize the TM?
b) export and import into an empty, new TM?
Yep, a) and b). At the moment the TMs are working but we update our master TMs on regular basis and when it comes to reorganizing we have to keep our fingers crossed that we don't get any errors.
4) Which kind of files were translated? If we are talking about tagged files (like ttx) you may like to consider the possiblity that there are tag errors in your TUs.
We only deal with Word an PowerPoint. Consequently we do not have any tagging information in the TMs.
We have not yet decided what to do. I see a problem in the missing upwards compatibility of TWB 5.5. We are a large authority and updating all installtions in one go is not possible. As a consequence we would have to keep Version 5.5 and Version 6.5 TMs. I think that managing subject based TMs is easier than managing different TM versions. Therefore we tend to split the TMs.