Aubéline Brandamir

Aubéline Brandamir said:

I've previously imported files from Memsource (.mxliff) and I always had visibility on the matches even without having the TM itself in Studio.

Where did you see these matches?

Hello Paul,

I don't have any issues with the Memsource files but only with the Wordfast files (.txlf). I can import them but I have no match whatsoever. The segments all appear as Translated but there is no match displayed.

When opened in WF, I do have matches

Aubéline Brandamir

Can you share the TXLF file?  Or can you open it with a text editor and show us a translation unit that should hve the match value in there?

I could share offline as this is confidential.

FYI, the segments showed should all have a match value

Aubéline Brandamir

ok - send it to pfilkin@sdl.com

Files sent just now

Thanks Aubéline Brandamir

I have your files and think I can explain like this.

The TXLF files provide the match values in the Alt-Trans element (so only for alternative translations) using this custom markup:

gs4tr:score="79"

The XLIFF specification uses this markup:

match-quality="79"

Studio displays the Alt-Trans information in the preview window, so your example you would see this with the TXLF file you have:

If you search replace all instances to use the XLIFF standard for the match-quality then you will see this instead:

I don't believe there is a mechanism in XLIFF for showing the match percentage of the actual translation unless it's in the alt-trans element.  Studio uses a custom element for this, and maybe if you use the mxliff plugin from the appstore it also provides this information for you?  But since there is no app available for TXLF you have to use the out of the box XLIFF filetype and this has no clue about Wordfast and their custom extensions, so you only have the alt-trans to go on and even there you need to correct it as I have done because they use custom attributes within the alt-trans element and not recognised values based on the XLIFF specification.

Thanks Aubéline Brandamir

I have your files and think I can explain like this.

The TXLF files provide the match values in the Alt-Trans element (so only for alternative translations) using this custom markup:

gs4tr:score="79"

The XLIFF specification uses this markup:

match-quality="79"

Studio displays the Alt-Trans information in the preview window, so your example you would see this with the TXLF file you have:

If you search replace all instances to use the XLIFF standard for the match-quality then you will see this instead:

I don't believe there is a mechanism in XLIFF for showing the match percentage of the actual translation unless it's in the alt-trans element.  Studio uses a custom element for this, and maybe if you use the mxliff plugin from the appstore it also provides this information for you?  But since there is no app available for TXLF you have to use the out of the box XLIFF filetype and this has no clue about Wordfast and their custom extensions, so you only have the alt-trans to go on and even there you need to correct it as I have done because they use custom attributes within the alt-trans element and not recognised values based on the XLIFF specification.

Hello Paul,

Thank you very much for this detailed explanation.

I do have the Wordfast plug in but indeed it does not display the scores. The mxliffs are however properly dealt with by Studio as all matches are displayed correctly.

So if I understand, I have no solution today. I've tried opening the .txlf files as .txt to manually change this so Studio could "read" it but the score does not appear there and the translation actually is not there anymore. I replaced all occurrences of "gs4tr:score" by "match-quality".

I'm surprised to be the 1st one to encounter this issue. Obviously I'm not the only one working with Studio and having clients using Wordfast (and txlf rather than .txml). I've tried exporting txml for Worfast Pro but it does not seem to be possible.

Maybe I should raise this "problem" somewhere for a developer to want to check this?

Aubéline Brandamir

Aubéline Brandamir said:

Maybe I should raise this "problem" somewhere for a developer to want to check this?

There isn't actually a problem here.  It's simply the result of two things:

1. Wordfast are using custom extensions other CAT tools are not aware of

2. There isn't a custom filetype for Studio that handles TXLF

If there was a demand for one we could create one and make it available through the appstore, but so far this is the first time I have seen anyone raise this as a problem they'd like to solve.  So it won't get much of priority with our community developers.

Hi,

I understand. I'm still very surprised no one "noticed" this before and needed visibility in Studio.

We could maybe give it a try and see if any of the developers is interested in creating a plug in?

Do you think it is worth trying?

I'm really not a big fan of Wordfast as I'm feel like I'm wasting a lot of time doing things I can do in minutes with Studio (and with confidence things are done the right way).

Hi, This is now becoming something that is really needed, considering a number of recent mergers and agencies beginning to force us to use Transperfect. I would really like to continue using SDL Trados Studio, which is a much more capable tool by far, but if I cannot see the memory match scores from Wordfast, I may be forced to abandon SDL Trados.

Please, please, please publish a filetype update or custom filetype that will make this possible.