• State Not Answered
  • Replies 6 replies
  • Subscribers 391 subscribers
  • Views 4350 views
  • Users 0 members are here
Options
Related

When we import one package manually, we get the question "The file X.sdlxliff contained in the package is older than the file in your project. Do you want to overwrite it?". When we import this package through the API, we get an error message.

Karl-Johan Grahn

We use Trados API to import packages. When we import one package manually, we get the question "The file X.sdlxliff contained in the package is older than the file in your project. Do you want to overwrite it?". When we try to import this package through the API, we get an error message as below. Our tool is called BatchRunner.exe.

"C:\Program Files (x86)\SDL\SDL Trados Studio\Studio5\BatchRunner.exe" /projectPackageFile=package.sdlppx /returnPackageFile=package.sdlrpx /exportDate="16/02/2017" /packageExportDir=C:\TEMP /so
INFO  28/Feb/2017 08:55:28: Starting to process targetLanguage: pl-PL
returnPackageDir: C:\Users\kgr\AppData\Local\Temp\ygkdnl41.zro
projectPackageDir: C:\Users\kgr\AppData\Local\Temp\vnj5ieco.pg3
INFO  28/Feb/2017 08:55:28: Percent complete: 0, StatusMessage:
INFO  28/Feb/2017 08:55:28: Percent complete: 0, StatusMessage: Opening package
INFO  28/Feb/2017 08:55:29: Percent complete: 30, StatusMessage: Importing files
INFO  28/Feb/2017 08:55:29: Message: Sdl.ProjectAutomation.Core.ExecutionMessage
INFO  28/Feb/2017 08:55:29: Percent complete: 30, StatusMessage:
ERROR 28/Feb/2017 08:55:29 Qlik.Trados.BatchRunner.Program.Main(:0): System.InvalidOperationException: This property is only available once the package has been imported.
 
It happens here:
ReturnPackageImport import = project.ImportReturnPackage(returnPackageFile, ProcessTaskStatusEvent, ProcessTaskMessageEvent);
 
We are using Trados Studio 2017.
 
Is this an issue on the vendor side, or is a Studio issue, or is it an API issue?
 
Can we automatically overwrite old bilinguals using the API?
 
When importing such a package manually there will also be an error when updating the TM - can the API handle that too with some setting?
Rate translation
×
Suggest better translation
×
Parents
  • 0
    I see this problem occasionally when importing same-day-turnaround return packages created in timezone which is behind the timezone where original translation package was created. The translated SDLXLIFF timestamps then seem to be older than the original untranslated ones, so Studio freaks out...
    I suppose that under normal circumstances this problem should not occur, but some translators/reviewers tend to have their machines configured very weirdly, so apparently a misconfigured date/time/timezone can cause such situation.
Reply
  • 0
    I see this problem occasionally when importing same-day-turnaround return packages created in timezone which is behind the timezone where original translation package was created. The translated SDLXLIFF timestamps then seem to be older than the original untranslated ones, so Studio freaks out...
    I suppose that under normal circumstances this problem should not occur, but some translators/reviewers tend to have their machines configured very weirdly, so apparently a misconfigured date/time/timezone can cause such situation.
Children