Translate
I have a large sentence archive from IBM Personal Translator that I am trying to import into Trados. It is not working. Any suggestions as to why?
I have a large sentence archive from IBM Personal Translator that I am trying to import into Trados. It is not working. Any suggestions as to why?
Which version has your tmx file? Is it valid? Are the language codes set properly? And on top of this: what kind of error message do you get?
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Which version has your tmx file? Is it valid? Are the language codes set properly? And on top of this: what kind of error message do you get?
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Dear colleagues (Richard and Jerzy),
I am following this thread because I have a similar problem.
The PM responsible for compiling the master TM in the agency sent the weekly TMXs to be imported into Studio and Trados Workbench. The PM sent two separate TMXs as usual. I have both CAT tools and this is the first time it ever happens.
When importing the Trados Workbench TMX, the tool reads all the translation units and imports none. They are all declared “invalid”. I opened the Studio TMX and imported it as usual. Then I saved it as compatible with Trados 2007 but, when trying to import it, the same error occurs. I downloaded two different plug-ins (SDLTMExport_Install and SDLTmConvert_v226_Setup) to try to solve this problem, but so far I have not been successful.
I would be very grateful if you could give me any input.
Kind regards,
You should be able to import the same TMX in Studio AND Workbench, as WB is able to read (and create) tmx 1.4b. Studio, though, must have 1.4b, other versions will not work. You can use Okapi Olifant http://okapi.sourceforge.net/downloads.html to check the tmx and to save it in 1.4 format accepted by Studio and Workbench.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Thank you, Jerzy! I will try your suggestion and let you know if it solved my problem.
Dear Jerzy,
I followed your instructions and I could not import the TMX into Trados WB. I even tried using the Olifant converter but it did not work. I opened the TMX file and tried to generate a TXT but the Olifant converter only reached 72% and stopped right there. I also tried importing the same TMX into Studio (it worked last week) and then saving it to be compatible with Trados WB, but it did not work.
Once again, thank you for your valuable help!
Please ask your vendor to send you the TMX again as a ZIP folder, as it seems the TMX has been damaged on its way to you. This happens sometimes with unzipped txt files. TMX is a plain text file in fact.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Sorry, I do not know what you mean by version. It comes from another translation programme - Linguatec Personal Translator. I always saved my archives in PT and tmx formats for exporting to other programmes. Do you mean by language codes Ausgangstext/Zieltext? If so, German/English. The message is: Import fehlgeschlagen. Die Datei konnte nicht verarbeitet werden.
So the TMX is damaged somehow. You can use Olifant (see above) to check, if the TMX works. But in this case I suppose the file is damaged, so either export again or ask for a new export.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
The most common problem with importing TMX files, if the file is well formed and a valid TMX, is the information in the header. Can you use a text editor to delete all the contents of your TMX apart from the header and the first translation unit, then share with us? Like this for example:
<?xml version="1.0" encoding="utf-8"?>
<tmx version="1.4">
<header creationtool="SDL Language Platform" creationtoolversion="8.1" o-tmf="SDL TM8 Format" datatype="xml" segtype="sentence" adminlang="en-US" srclang="en-US" creationdate="20170918T092759Z" creationid="GLOBAL\pfilkin">
<prop type="x-Model:SinglePicklist">Aston Martin,Austro-Daimler,Bugatti,Duesenberg,Ferrari,Horse Carriage,Jaguar,McLaren,Mercedes,Shelby,Stanley</prop>
<prop type="x-Year:Integer"></prop>
<prop type="x-Quality:Integer"></prop>
<prop type="x-SourceFile:SingleString"></prop>
<prop type="x-TargetFile:SingleString"></prop>
<prop type="x-Recognizers">RecognizeAll</prop>
<prop type="x-IncludesContextContent">True</prop>
<prop type="x-TMName">en(US) - de(DE) {Fastest Production Cars}</prop>
<prop type="x-TokenizerFlags">DefaultFlags</prop>
<prop type="x-WordCountFlags">DefaultFlags</prop>
</header>
<body>
<tu creationdate="20170918T093522Z" creationid="GLOBAL\pfilkin" changedate="20170918T093844Z" changeid="GLOBAL\pfilkin" lastusagedate="20200817T084158Z" usagecount="1">
<prop type="x-LastUsedBy">GLOBAL\pfilkin</prop>
<prop type="x-Context">0, 0</prop>
<prop type="x-Origin">TM</prop>
<prop type="x-ConfirmationLevel">Translated</prop>
<prop type="x-Year:Integer">1880</prop>
<prop type="x-Model:SinglePicklist">Horse Carriage</prop>
<tuv xml:lang="en-US">
<seg>I know, I know, this is not a car, it’s a horse-drawn carriage — but we needed a reference point.</seg>
</tuv>
<tuv xml:lang="de-DE">
<seg>Ich weiß, ich weiß, das ist kein Auto, sondern eine Pferdekutsche - aber wir brauchten einen Bezugspunkt.</seg>
</tuv>
</tu>
</body>
</tmx>
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
The TMX was sent in a zipped file. I sent the TMX to another collegue with the same Trados version and she got an error message: Error:(35000): SSYacc0103e: Attempted read past eof. Instead of reading all the TU and declaring them invalid, she got this error message. We have tried everything but the problem remains.
I would suggest that you open the TMX file in let’s say in Notepad and check carefully the header and the footer of the file. Compare it with a TMX file where this problem did not occur. I had this problem once or twice as in the footer some lines were missing, such as
</tu>
</body>
</tmx>
After I added this lines in notepad it worked.
If this does not work you will have to convert it to txt file, check the content (source and target and formatting features) and then convert it into sdltm using the tool below (see link). But this step requires some knowledge about the nature of xml files.
Please note that the 2021 version of SDL does not support the import of a TMX file any more (which was very practical in the previous versions when an exchange of memory files was needed). You will have to use the newest Glossary converter, who includes now as well the conversion of a TMX file to SDLTM. (link: www.cerebus.de/.../ ).