Detecting language please wait for.......
I was wondering if the latest Groupshare SR1 has resolved the issue of importig more than TMX into the same language pair at the same time (by two users in parallel). Currently, when this happens, one import tasks gets queued.
Has the issue with the "Keep most recent option" been fixed? It has been solved for tile based TMs but I can't see any reference to this being fixed for GroupShare TMs. Updating TMs using the “Keep most recent” option did not populate the TU fields with both the existing and the new field values. This is now fixed and the TUs are updated with the merged field values when the “Update TM” batch task or an import is performed. (CRQ- 16388)
I hope my reply finds you well and safe.CRQ-16388 has been addressed and a fix was applied in the Translation Memory service, used by both Studio and GroupShare. With the latest available…
I hope my reply finds you well and safe.CRQ-16388 has been addressed and a fix was applied in the Translation Memory service, used by both Studio and GroupShare. With the latest available builds, this is fixed. Needless to say, that if you have reasons to believe this is not, the best approach would be to engage support via a case.Regarding your first question, yes this available since GS 2020 CU2. Importing more than one TMX into the same language did not properly work - but this is no longer the case and the 2nd import (for example) can be queued, but it starts as soon as the first import finishes.I hope this helps.Best regards,Radu
That sounds very good, Radu. Thanks for confirming!