Marcela Sciaccaluga

I think the version of Studio you are using is the most likely suspect, but the problem could be in Studio or memoQ... hard to know.  If you can share an example ofthis I'd be happy to test it as I do have both Studio and memoQ.  I have 2015 and 2019 for Studio so can check in both, bit only have the latest version of emoQ so can't comment on how that may affect things.

You can email me, pfilkin@sdl.com with the files, if this is acceptable?

Hello, Paul, sure! Thanks! The client thinks it's a Trados problem because their engineers did a test and that's what they found apparently.

I will email the files shortly, thanks!

Marcela Sciaccaluga

Thats for sending me the files. The problem is that memoQ seems to have changed the mqstatus attribute they use in their XLIFF for translated files.  They probably have several statuses for "translated" now and I don't know what they all are... but for sure they use this:

mq:status="ManuallyConfirmed"

Studio exports with this status:

mq:status="Translated"

We don't differentiate between the way a file was confirmed in this attribute, we use something else for this.  Just one of the problems of the XLIFF standard... it's too loose.

So for now the solution is still pretty simple... just unzip the mqxlz file created by Studio to a folder somewhere.  Search and replace this:

mq:status="Translated"

with this:

mq:status="ManuallyConfirmed"

Then save the files and zip them up again, finally renaming back to whatever the original mqxlz was called.  This way when they are opened in memoQ all the translated segments will appear as translated in memoQ.

In the meantime I have emailed a development contact in memoQ to ask for a list of all the statuses they now use.  Once I have this I'll request a change in Studio to support the new statuses correctly.

Marcela Sciaccaluga

Thats for sending me the files. The problem is that memoQ seems to have changed the mqstatus attribute they use in their XLIFF for translated files.  They probably have several statuses for "translated" now and I don't know what they all are... but for sure they use this:

mq:status="ManuallyConfirmed"

Studio exports with this status:

mq:status="Translated"

We don't differentiate between the way a file was confirmed in this attribute, we use something else for this.  Just one of the problems of the XLIFF standard... it's too loose.

So for now the solution is still pretty simple... just unzip the mqxlz file created by Studio to a folder somewhere.  Search and replace this:

mq:status="Translated"

with this:

mq:status="ManuallyConfirmed"

Then save the files and zip them up again, finally renaming back to whatever the original mqxlz was called.  This way when they are opened in memoQ all the translated segments will appear as translated in memoQ.

In the meantime I have emailed a development contact in memoQ to ask for a list of all the statuses they now use.  Once I have this I'll request a change in Studio to support the new statuses correctly.

Thanks so much for taking the time to help us out!

Paul said:

The problem is that memoQ seems to have changed the mqstatus attribute they use in their XLIFF for translated files. 

I was going to say that... this is actually a pretty old news:
https://community.sdl.com/product-groups/translationproductivity/f/studio/15446/mqxlz-tags-in-sdl-trados-studio
https://community.sdl.com/product-groups/translationproductivity/f/studio/16760/mqxliff-segment-status-mapping

Different problem... but certainly the changed statuses were an issue then.  I have no idea if the current memoQ statuses are exactly the same as they were two years ago or not, or what all the statuses are.  But clearly there are still issues to resolve.

Different problem originated the discussion, but the statuses were changed already by that time, as the second discussion - which happened only a month later - showed ;-)

And I wonder what the CRQ-8536 mentioned in one of the threads is doing by now ;-)