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.
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
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/.../ ).
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/.../ ).
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/.../ ).
rhis is nonsense. Of course 2021 supports the import of a TMX. The only change in 2021 is you need the power pack from the AppStore if you want to be able to use a Quick Upgrade where you select the TMX as the TM. Importing is the same as it always has been.
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
Well, it was per se integrated in the last versions, and you did not need to download any additional apps.
It’s integrated in 2021 as well. You do not need to download additional apps to import a 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
Where? If I choose Translation memory in SDL 2021 the only option is sdltm.
That’s because you are confusing Open with Import!
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
I do not use open with import when creating a new project as this option is inactive and becomes available only after a sdltm file has been chosen. So this question is not solved. All I want is using a tmx file that has been exported from e.g. MemoQ or any other translation program, which is used as the only memory in SDL without any import. In other words SDL should convert it to a sdltm file so that it can be used during translation.
So this question is not solved.
You're right. It's not solved because the user has still not responded. The question was how he imports his TMX into Studio because he has a problem with the file. You responded and gave him some reasonable advice on how to edit the TMX to achieve this, but then you made a comment that is completely incorrect. You said:
Please note that the 2021 version of SDL does not support the import of a TMX file any more
This is incorrect. It absolutely does does support the import of a TMX and always has done.
It's now clear that you are not importing at all. You are simply using the TMX as your TM and converting it to an SDTM on the fly using the quick upgrade feature. This capability was indeed removed in 2021. I think it was a mistake to remove it, but nonetheless you can get this feature back by installing this app:
https://appstore.sdl.com/language/app/sdl-trados-compatibility-and-migration-power-pack/1101/
You can read why this was removed here:
https://multifarious.filkin.com/2020/08/15/some-you-win-some-you-lose/
So, if you have some other question you want answered I suggest you create a new thread so we can mark this onet as resolved if we manage to do so when the user responds.
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
Sorry for the delay. What I am now hoping to learn is how to use Olifant to enable me to export my Linguatec tmx file into a Trados tmx file. Do you know how to do this?
What I am now hoping to learn is how to use Olifant to enable me to export my Linguatec tmx file into a Trados tmx file. Do you know how to do this?
I wouldn't even entertain this route without seeing the file first. Can you provide the details I asked for earlier?
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
I wanted to send a text file with an example, but I got the following message: Leider kann das Dokument x nicht geöffnet werden, da sein Inhalt Probleme verursacht.
Details: Ungültiges Unicode-Zeichen
Position: Zeile 566623, Spalte 112