You can use a plugin designed specifically for this, SDLXLIFF Split/Merge.īut be careful. There are different methods for cutting a big SDLXLIFF Trados Studio file into several smaller ones. If you know a more humane method, please share. And if your XLF file is small and the translation memory does not reduce the amount of work, you can translate it by opening in Trados Studio directly, i.e., even without creating a project. The instruction seems long, but it takes actually longer to write than do what it tells: it is important to understand the purpose of each action though. Then, you will probably have to either upload the package to SDL WorldServer (if you have done everything correctly, the server will accept it) or send it to your client, depending on your procedures.
#Trados studio 2017 achat zip
#Trados studio 2017 achat archive
#Trados studio 2017 achat how to
You need to convert it from TBX to SDLTB first-we will tell you how to do it in one of the future posts because this one is already getting huge :) If the unzipped archive contains a TBX file, connect it as a termbase.In the project, create an empty translation memory and import the TMX file from the unzipped archive into it.Specify the XLF file from the unzipped archive as a file for translation.Manually create a project in Trados Studio with the name repeating the name of the source package and the same language direction.Rename the package file: replace the WSXZ extension with ZIP or just add the ZIP extension.Their common purpose is to retrieve the XLF file from the package and translate it separately. If the client is unavailable or has no idea about how to solve it, perform the operations below. Surprisingly, the problematic XLF file itself gets opened as intended (in our case).įirst, you should inform your client about the issue. The exact origin this issue is unknown, but it is related to some problems with the XLF file structure. The error is rare: Google knows about it by hearsay, and even if you use the link, you will find the description of termbase issues, but the real reason turned out to be different. Attempted to divide by zero error appears when you try to import a WSXZ package. The fascinating TV show about Trados Studio errors continues!