Creating project-independent TMs in Transit NXT
Thread poster: Dan Lucas

Dan Lucas  Identity Verified
United Kingdom
Local time: 06:05
Member (2014)
Japanese to English
Aug 12, 2016

For the past month or so I have been using Transit NXT SP 9 for a client, translating a steady stream of often interesting documents in one of my areas of specialisation. While I definitely prefer SDL Studio, Transit has not been as difficult as its reputation may suggest.

Having said that, I am still a long way from being comfortable with the software. One thing that I would like is the equivalent of a TM that is independent of the project terminology. I may do a dozen (fairly short) projects per week and these projects often refer back to previous projects (but without any explicit link).

I would like my own translation memory that runs in parallel with the project-specific TMs, so that I can build up a TM of my own choice with regard to these jobs. Is this possible and if so how would I go about it?

Thanks
Dan


 

CafeTran Training (X)
Netherlands
Local time: 07:05
Yes you can Aug 13, 2016

Dan Lucas wrote:

Having said that, I am still a long way from being comfortable with the software. One thing that I would like is the equivalent of a TM that is independent of the project terminology.


As you probably may have noticed, Transit stores its memories als xml language pairs that are aligned. You can import your master TM from Studio as TMX. Transit will create a language pair of it.

During the configuration of a new project you can include this language pair as your master TM. Note that Transit won't commit your new project's segments to the master.

Another approach is to store the master language pairs in a separate folder (e.g. \transit\projects\bigmama). When you create a new project, you can include this folder as a reference project. When you have completely finished the project, copy the project related language pair(s) to the bigmama folder.

Note that Transit won't remove duplicate segments. You can fine tune which translations should be used, based on a large set of parameters. But in the end you'll have tons of language pairs that may contain many identical segments. If you spot a typo or want to make another change to the translation of a segment or term, you'll have to open all these language pairs. So you'll start making an extract from bigmama, that only contains unique segments. Which is more or less against Transit's philosophy of project related TMs. All in all too much work and I upgraded to a more advanced CAT tool icon_wink.gif.


 

Dan Lucas  Identity Verified
United Kingdom
Local time: 06:05
Member (2014)
Japanese to English
TOPIC STARTER
First steps Aug 15, 2016

CafeTran Training wrote:
All in all too much work and I upgraded to a more advanced CAT tool icon_wink.gif.

Yes, I would prefer to be using Studio, but unfortunately the end client's systems are built around Transit so that is not going to change. Given the amount of interesting work I am prepared to compromise on that.

Thank you for your comments; I will use them as a base to explore my options. The main issue is that each project consists of several different sub-topics, and each of these topics may persist through several projects. However, the project number does not give any clues as to what it contains, so establishing which past projects are relevant to the one in hand is... vexing.

Regards
Dan


 
Project related vs. project independet TM Aug 29, 2016

Another approach is to store the master language pairs in a separate folder (e.g. \transit\projects\bigmama). When you create a new project, you can include this folder as a reference project. When you have completely finished the project, copy the project related language pair(s) to the bigmama folder.

You can simplify that by using the "Copy current project to reference folder" function (in the bottom on the "Reference material" tab). If you tick the "Use as default" option, this needs only three clicks at the end of each project.

If you spot a typo or want to make another change to the translation of a segment or term, you'll have to open all these language pairs.

Not necessarily. If you spot a typo, you just can open the ref segment (with the red-green icon in the Fuzzy window) and change it -- typo corrected.
To do "mass changes", note you can open *all* reference files in one go and display/check/edit them as if they were *one* single file -- including complex search/replace operations and using smart filter functionality.

So you'll start making an extract from bigmama, that only contains unique segments. Which is more or less against Transit's philosophy of project related TMs. All in all too much work and I upgraded to a more advanced CAT tool icon_wink.gif.

On the other hand: In Transit, you have to option: Handle TMs project related or generic. I prefer having a choice and *not* being forced to pour any reference segments in a huge black box, loosing any context and without having a clue which suggestions comes where from. Pouring anything in one pot is less work at the first glance, but may cost a lot of time and quality in the long run. This is at least my experience, but depends on the projects and the personal approach.

Regards,

O.N.


 


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

Moderator(s) of this forum
Maya Gorgoshidze[Call to this topic]

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

Creating project-independent TMs in Transit NXT

Advanced search






SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running, helps experienced users make the most of the powerful features, ensures new

More info »
SDL Trados Studio 2019 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2019 has evolved to bring translators a brand new experience. Designed with user experience at its core, Studio 2019 transforms how new users get up and running and helps experienced users make the most of the powerful features.

More info »



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