Upgrading TMs leads to huge increase in file size - is it possible to reduce it?

Hello,

I've recently upgraded a TM which went from 285 MB to 1G. This creates huge packaqes, long download times and disk space issues. Is it possible to reduce the TM size? Or how can we best handle large TMs with our translators?

Thanks,

Valerie

Parents


  • Have you used Project TMs? One purpose of these is to ensure you only include a TM that contains material relevant to the translation and are therefore smaller.

    You can't reduce the size of an upgraded TM without recreating it without the additional information used for upLIFT features.

    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

  • Just out of curiosity
    How can I make 'Project TM' ? Can you tell me related information ?
    I have never used 'upLIFT' function and feels like will never use it.
    It is not so good choice to make TMs larger 3 times then ever.
  • Unknown said:
    How can I make 'Project TM'

    When you create a project, a standard project and not a single file translation project, you are asked whether you wish to "Prepare without project TM" which is the default, or "Prepare".  There are other options but these two are the relevant task sequences for this discussion.

    "Prepare without project TM"
    This will create the project and include any TM you have added to the project and subsequently insoide a Project Package if you choose.  It uses the whole TM.

    "Prepare"
    This will create the project as above, but it will use the TMs you selected to create a smaller TM that only consists of TUs that match the content of your Project.  It will use the fuzzy match lookup settings to decide how much to include.  So if you the default setting of 70% fuzzy it will include any TUs that would provide a 70% fuzzy match lookup and above.

    The advantage of this is you can prepare your Project Package and include a smaller, yet still relevant, TM for the recipients of your package to use and you don't have to send a huge translation memory.

    There are other benefits... for example.  If you like to keep tweaking your translation and don't want to commit it to your TM until you have finished your final review then instead of not confirming your work (which I have seen some people do) you can use a Project TM.  When you work it will all be saved into the Project TM and not into your Main TM.  You will still get results from your Main TM so having a larger TM for concordance can be useful for example, but you won't actually add any of your work to your Main TM.  Then when you are completely happy you can run the Update Main TM batch task and this will also update your Main TM.  Funnily enough this is often the reason for some users thinking nothing is updated to their TM as they work.  They prepared the project using a project TM and then keep checking inside their Main TM to see the results... which are not there yet!

    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

Reply
  • Unknown said:
    How can I make 'Project TM'

    When you create a project, a standard project and not a single file translation project, you are asked whether you wish to "Prepare without project TM" which is the default, or "Prepare".  There are other options but these two are the relevant task sequences for this discussion.

    "Prepare without project TM"
    This will create the project and include any TM you have added to the project and subsequently insoide a Project Package if you choose.  It uses the whole TM.

    "Prepare"
    This will create the project as above, but it will use the TMs you selected to create a smaller TM that only consists of TUs that match the content of your Project.  It will use the fuzzy match lookup settings to decide how much to include.  So if you the default setting of 70% fuzzy it will include any TUs that would provide a 70% fuzzy match lookup and above.

    The advantage of this is you can prepare your Project Package and include a smaller, yet still relevant, TM for the recipients of your package to use and you don't have to send a huge translation memory.

    There are other benefits... for example.  If you like to keep tweaking your translation and don't want to commit it to your TM until you have finished your final review then instead of not confirming your work (which I have seen some people do) you can use a Project TM.  When you work it will all be saved into the Project TM and not into your Main TM.  You will still get results from your Main TM so having a larger TM for concordance can be useful for example, but you won't actually add any of your work to your Main TM.  Then when you are completely happy you can run the Update Main TM batch task and this will also update your Main TM.  Funnily enough this is often the reason for some users thinking nothing is updated to their TM as they work.  They prepared the project using a project TM and then keep checking inside their Main TM to see the results... which are not there yet!

    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

Children