Exporting a Server TM using the TranslationMemory API results in a TMX file that misses the context matching information

Question

Hi, originally, I posted this question here, but I think I chose the wrong forum at least there was zero feedback ... So I post here again and hope to receive feedback here 
 
 I have detected a problem with the Exporter class in the TranslationMemory API. The problem is that - when a server TM gets exported, the TMX is missing the context information after the export. 
 Here is my code: 
 Dim TMExporter As New Sdl.LanguagePlatform.TranslationMemoryApi.TranslationMemoryExporter(ServerBasedTranslationMemory.GetLanguageDirection(LangDir)) 
 TMExporter.ChunkSize = 100 
 TMExporter.FilterExpression = GetFilterCreatedAt() 
 AddHandler TMExporter.BatchExported, AddressOf Exporter_BatchExported 
 strExportfile = ExportFolder & "\" & ServerTM & "_" & LanguageDirection.SourceLanguageCode.ToString & "_" & LanguageDirection.TargetLanguageCode.ToString & ".tmx" 
 Try 
 Dim strNow As String = Now.ToString( "yyyyMMdd_HHmmss" ) 
 TMExporter.Export(strExportfile, True ) 
 System.IO.File.AppendAllText(LogFile, ControlChars.CrLf & strNow & " SUCCESS: " & ServerTM & " , Source Language: " & LanguageDirection.SourceLanguageCode.ToString & " , Target Language: " & LanguageDirection.TargetLanguageCode.ToString & " was successfully exported to " & strExportfile & ". " & exportProgress.ToString & " TUs were exported." & ControlChars.CrLf) 
 Catch ex As Exception 
 Dim strNow As String = Now.ToString( "yyyyMMdd_HHmmss" ) 
 System.IO.File.AppendAllText(LogFile, ControlChars.CrLf & strNow & " ERROR: " & ServerTM & " , Source Language: " & LanguageDirection.SourceLanguageCode.ToString & " , Target Language: " & LanguageDirection.TargetLanguageCode.ToString & " could not be exported. The original error message was: " & ex.ToString & ControlChars.CrLf) 
 System.IO.File.Delete(ExportFolder & "\" & ServerTM & "_" & LanguageDirection.SourceLanguageCode.ToString & "_" & LanguageDirection.TargetLanguageCode.ToString & ".tmx" ) 
 End Try 
 This code - when run on a local SDLTM exports everything just fine including the context information:

But when I run it on a server TM, the TMX misses the context information after the export finishes:

I can also export the server TM from Trados Studio and from the Groupshare Web UI just fine and the exports always include the context information. 
 Also, as I said before - export from a SDLTM through the API also creates a TMX that includes the context information. 
 
 It is really only the export from a server TM through the TM API that loses the context information. Is this a known issue? It basically means that - whereever automation of exporting TMX from server TMs is used to backup the TM data, this will currently lose the context information.

Daniel Brockmann · Answer

Hi Tom Imhof - there is indeed a known issue in the API when retrieving the list of GroupShare TMs, however you can work around it in your code by making certain small changes. I would ask Andrei Caia to explain the workaround here when he has time. Also tagging Paul Petrehus . Thanks, Daniel

Patrick Andrew Hartnett · Answer

Hi Tom Imhof , I have just received information from Paul Petrehus that you should use "GetTranslationMemoriesByQuery(TranslationMemoryEntityQuery query)" to get the TMs + avoid this exception. 
 Can you try this an let me know how it goes?

Patrick Andrew Hartnett · Answer

Hi Tom Imhof , thank you for confirming this (y). I confirm that I can also reproduce the original issue you reported against GS server CU9 using TranslationMemoryExporter . I overlooked this as I've always used ScheduledServerTranslationMemoryExport for server based memories as it is the more optimal approach, especially over slower network. 
 You're absolutely correct, the content of the exported TMX should be the same irrespective of the users choice in using the scheduled export or not. Daniel Brockmann , I'll escalate this issue to the dev team.

Patrick Andrew Hartnett · Answer

Please try the following and let me know how it goes. 
 string sourceFilePath = "compressed.gz"; // Replace with your source GZip file path
string extractedFilePath = "extracted.txt"; // Replace with the desired output file path

try
{
 using (FileStream sourceFileStream = File.OpenRead(sourceFilePath))
 using (FileStream extractedFileStream = File.Create(extractedFilePath))
 using (GZipStream gzipStream = new GZipStream(sourceFileStream, CompressionMode.Decompress))
 {
 byte[] buffer = new byte[4096];
 int bytesRead;

while ((bytesRead = gzipStream.Read(buffer, 0, buffer.Length)) > 0)
 {
 extractedFileStream.Write(buffer, 0, bytesRead);
 }

Console.WriteLine("File extraction complete.");
 }
}
catch (Exception ex)
{
 //TODO
}

Community Jira · Answer

An issue has been created on Jira with the internal tracking nr. CRQ-35250

Patrick Andrew Hartnett · Answer

Hi Tom Imhof , I have reviewed this issue today, but unable to reproduce the issue that you are reporting. 
 Prerequisites 
 
 Trados Studio 2022 SR1 - 17.1.6.16252 
 GS: 15.1.9.12529 - GS 2020 SR1 CU09 
 
 Steps 
 
 Create a server based tm from GroupShare 
 Open the server based TM in Stduio & add some custom fields 
 Add a few TU entries & assign a custom field value to one or two of the TU's 
 Commit changes so that they are updated on the server. 
 Create a standalone app to connect and export the server based TM to tmx 
 
 Documentation: How to export serverbased TM to TMX

Actual result 
 The custom field values are exported correctly, visible from the TU's in the TMX that was exported from the serverbased TM 
 
 Follow up 
 Tom Imhof Can you pls provide the GroupShare version + Trados Studio version you are using?

GroupShare Developers > GroupShare Developers forum

Exporting a Server TM using the TranslationMemory API results in a TMX file that misses the context matching information

Top Replies