Maharasi Murugan

I'm afraid this post needs more information to be able to support you.

1. the screenshots are illegible... too small
2. you need to provide an XLIFF/TMX for us to check
3. you need to confirm if you can import these into a clean, new SDLTM, or if this is only a problem with importing into some existing TM?
4. you need t confirm if you are importing into a file-based TM or a server-based TM?

 Hello Paul,

I have re-uploaded the screenshots. As a translation team, we do the TM consolidation every month and we have had no issues until now. This month some users got errors (they had updated their trados recently) and we asked other users to try importing the same set of xliffs/TMX and found that users with previous versions were able to do it without any error and it failed only for users who updated their trados to the new version. We are importing file-based TMs.

Due to confidentiality issues, we are unable to share the xliffs/TMX but I can confirm that we could reproduce the import error in every user who had the latest version. These users were able to export their XLIFFs into TMX but importing TMX into an existing TM failed. However, we were able to import into a blank/SDL TM. As seen in the screenshot below, the “show error details button” was greyed out for these users. Initially, we thought it was file-specific problem or due to corrupt TM and retried TM consolidation using the previous month’s backup (which was successful for these same users for the same set of files and TM last month) but it failed for them this time.

In fact, for one of the users who faced this issue, we uninstalled Trados and installed the previous version and import is working fine for him now. Please let me know if you need more details.

Thanks,

Maharasi

 Hello Paul,

I have re-uploaded the screenshots. As a translation team, we do the TM consolidation every month and we have had no issues until now. This month some users got errors (they had updated their trados recently) and we asked other users to try importing the same set of xliffs/TMX and found that users with previous versions were able to do it without any error and it failed only for users who updated their trados to the new version. We are importing file-based TMs.

Due to confidentiality issues, we are unable to share the xliffs/TMX but I can confirm that we could reproduce the import error in every user who had the latest version. These users were able to export their XLIFFs into TMX but importing TMX into an existing TM failed. However, we were able to import into a blank/SDL TM. As seen in the screenshot below, the “show error details button” was greyed out for these users. Initially, we thought it was file-specific problem or due to corrupt TM and retried TM consolidation using the previous month’s backup (which was successful for these same users for the same set of files and TM last month) but it failed for them this time.

In fact, for one of the users who faced this issue, we uninstalled Trados and installed the previous version and import is working fine for him now. Please let me know if you need more details.

Thanks,

Maharasi

Maharasi Murugan

Maharasi Murugan said:

Due to confidentiality issues, we are unable to share the xliffs/TMX but I can confirm that we could reproduce the import error in every user who had the latest version.

ok - thank you.  If we manage to reproduce this it'll be addressed.

I can corroborate Maharasi's issue here. I am experiencing the same issues with importing .tmx files to current TMs and to brand new TMs. Also cannot update a TM from a completed SDL project file.

Joanne Green

Perhaps you can provide a TM and a TMX/SDLXLIFF where this fails so we can investigate it?

Do you have a secure location I can share them with you?

Joanne Green

You can email them... or send me a link to dropbox or something similar?  pfilkin@sdl.com

Joanne Green

Thanks for sending me the files.  I could reproduce this using the latest version of 2019.  I could also solve the problem by upgrading the SDLTM first:

Perhaps try that and see how you go as this worked for me.  There was nothing in the TMX to import however as all the segments seem to be in the TM already... I did spot-check a few of them... but the error was gone.

Maharasi Murugan perhaps you can try this with your TM's?

Yes, my colleague who hasn't yet upgraded imported the tmx for me already, that's why the segments are already in the TM.
I'm afraid upgrading every SDLTM first is not a viable solution for us. We have over 300 active TMs.
Do you anticipate a patch release to fix this at source?

Joanne Green

Joanne Green said:

Do you anticipate a patch release to fix this at source?

No.  The upgrade process is required to support fragment matching properly.  If there was a patch release it would involve upgrading your TMs.

I imported tmx/xliffs after upgrading the TM and it worked for one of the users but only few segments were imported (for users with previous versions, much more segments were imported for the same tmx/xliffs). For the other user, the import/export option went missing after using the Upgrade memory option. So, now we are having another problem . This TM merge activity is really important for us and our clients and we would like it to work smoothly as it was the case before. I really hope the it gets fixed.