MinJoo Jang

MinJoo Jang said:

I've heard that there is a connector for XTM <-> Studio.

Where did you hear this?

MinJoo Jang said:

How can I convert XTM file to Studio file and vise versa?

This should be trivial... XTM can export an XLIFF file and Studio can handle it as for any file you would open in Studio.

Hi, Paul

I've heard this information from my manager.

So, there is no special connector, right?

I'll try to export Xliff from XTM.

MinJoo Jang

We did actually develop one internally, but we did not release it.  The reason for this is twofold:

• XTM charge for the use of their API and we didn't have a customer who was prepared to pay for this so we didn't progress the work
• All users connecting through the API need to have Project Manager permissions so this also limits its use
• XTM is short of endpoints for updating the translated files via the API so this would have to be manual anyway. XTM have said they intend to rectify this but have not provided any timescale or a commitment to deliver it.  There are also some restrictions around the use of Translation Memories but these are less of a problem I think.

So with all of that in mind we did not progress thi work.  We have a working plugin in as far as it goes but it will probably be of little use to you unless the instance you are working with is API enabled.  I can let you test it if you like, but you should check for the above first.

Hi Paul,

Let's see if I understrand it clearly. My translation company has migrated from Trados to XTM. I hate XTM but there is the possibility to export the XLF files to work offline. The problem is that this creates a XLF that Trados does not handle properly, the reason being that Trados destroys all fuzzy match information and confirms all segments even if they were not confirmed in the XTM cloud. Bear in mind than in the XTM there may be the following segments: 

1. 100&ICE segments that are exported as Translation Approved to Trados and locked.

2. Fuzzy matches coming from applications of TM's, which are exported to Trados as Translated and fuzzy match information is destroyed.

3. Manually translated segments which are exported to Trados as Translated and fuzzy match information is destroyed. (no way to differentiate this correctly finished segments to the incomplete segments above!)

4. Empty segments  which are exported to Trados as Not translated.

Of course the problem lies in point 2. We make an intensive use of fuzzy matches and TM and all that information appears in Trados as Translated and the fuzzy match information

Do you think your trados plugin could help me with this? I have been tweaking the XLIFF file type settings but nope, nothing changes. Fuzzy match information is destroyed and all unconfirmed segments are confirmed and appear as Translated in Trados.

Funnily enough, poings 1, 3 and 4 are correctly processed. But point no. 2 makes working with Trados impossible. Any ideas or any plugin or any settings modification I could use? I reaslly dislike working with XTM, working with Trados is twice as fast.

Hi Ignacio,

Same with me, one of my customers works in XTM and I am thinking about opting out completely. Very tiresome that tool. Any news regarding your No. 2?

Same here. XTM is the most overhyped tool in the market now, and it is very tiresome and has a huge impact on my productivity. I have no clue why all customer are adopting this silly tool. I hope XTM allows offline load of their packages in Trados soon. 

Same here. XTM is the most overhyped tool in the market now, and it is very tiresome and has a huge impact on my productivity. I have no clue why all customer are adopting this silly tool. I hope XTM allows offline load of their packages in Trados soon.