Studio 2014 - allowing multiple translations by using different field values
Thread poster: tz7

tz7
United States
Local time: 19:50
English to Japanese
May 17, 2014

I know you can add different translation for the same source text by "Add as New Translation" but it can't be automatic?

In Trados Workbench, if the project setting is different, you can add the new translation as a new TM entry. In Studio 2014, even I set a different values (in Project Settings > language pairs > Translation Memory and Automated Translation > Updates), the new translation overwrites the old translation in the TM and leaves its "old" values in the new translation. Because of this, I can NOT keep different translations for different projects in the TM. Is there any option or tweak to achieve the same behavior as Workbench, rather than I selectively use "Add as New Translation"?

If the project setting is identical, the old translation should be overwritten by the new one. I don't know the reason why Studio updates translation and leaves old field values with the new values in TM.


 

SDL Community  Identity Verified
United Kingdom
Local time: 01:50
English
The reasoning... May 27, 2014

Hi,

There are differences in handling here, and these stem from the problems many users encountered in working with fields to control this behaviour in Trados. So in Studio we have attempted to make this easier.

  • Field values are no longer used for making a TU unique. The (most of the time implicit) uniqueness was always the thing that created the headaches for Workbench users. You had to be very careful to set the right values and then hope that different TUs would be created; you could never be 100% sure about this.
  • The only thing you need to remember now is to use Add As New Translation. In that case:
    • A new TU will be created with the currently defined fields – they will be unique to this TU if the translation has to be different from other TUs.
    • In all other cases (where translation does not need to change – which is the vast majority of cases) the fields will always be merged into TUs as needed.

So fields will always be merged when the translation does not change, and when it does need to change, or you want to add a new TU anyway then just think of Add As New Translation. This is easier and less confusing.

Regards

Paul


 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Studio 2014 - allowing multiple translations by using different field values

Advanced search







Déjà Vu X3
Try it, Love it

Find out why Déjà Vu is today the most flexible, customizable and user-friendly tool on the market. See the brand new features in action: *Completely redesigned user interface *Live Preview *Inline spell checking *Inline

More info »
Protemos translation business management system
Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!

The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search