| User | Thread poster: Bjørnar Magnussen T2007: Unable to import a TMX export from T2009 |
|---|
Bjørnar Magnussen 
Norway
Local time: 11:26
  Member (2002)
English to Norwegian
+ ...
MODERATOR |
A customer is asking for a Trados 2.x - 6.x format export of a project that I have translated in Trados 2009.
Since Trados 2009 don't let me export to this format, I figured out that I had to export to TMX, import the TMX file in Trados 2007 and then export to Trados 2.x - 6.x from there.
However, no matter what file type (TMX 1.1, 1.4 or 1.4b) I choose in the import dialogue in T2007, I always get "0 added, xxx invalid TUs".
The languages of the T2007 TM and T2009 export are exactly the same.
Have any of you been able to import a T2009 TMX export into T2007?
| | | |
Claudia Alvis
United States
Local time: 04:26
English to Spanish
+ ...
|
I have, a few times. Check your filter settings, maybe something is preventing the TUs from being imported. Also, make sure you have full access to the TM in Trados 2007.
| | | |
Bjørnar Magnussen
Norway
Local time: 11:26
Member (2002)
English to Norwegian
+ ...
MODERATOR TOPIC STARTER | | TMX 1.1, 1.4 or 1.4b? | Jun 30 |
Thanks a lot for your quick answer, Claudia. I will experiment further. Which format did you choose when importing into Trados 2007 - TMX 1.1, 1.4 or 1.4b?
| | | |
Bjørnar Magnussen
Norway
Local time: 11:26
Member (2002)
English to Norwegian
+ ...
MODERATOR TOPIC STARTER |
I opened the TMX in Notepad++ and changed all the language codes from "NB_NO" to "NO_NO" - then it worked
| | | |
Claudia Alvis
United States
Local time: 04:26
English to Spanish
+ ...
|
In Studio, there's no option to set the version of the TMX files. Under 'Save as type', there's only TMX Files and TMX Compressed Files. You should select the first one. Then in Trados, I always select 1.4b; for no particular reason really, I figure that it's the newest one. But I just exported a Studio TM and imported into a new Trados TM, I used the three TMX formats, and was able to add all the terms without any problems.
Nevermind, I just read your new post. I guess it's one of those "small" issues that shouldn't been there in the first place.
| | | |
BenB
Spain
Local time: 11:26
Norwegian to English
|
Thanks for posting the solution you found, Bjørnar - I did the same thing after having the same problem and was able to import the TMX file successfully. I don't know whether this only affects translation memories with Norwegian as one of the languages, or whether it's a more general issue, but either way it appears to be a bug.
| | | |
SDL Support
United Kingdom
Local time: 10:26
English
| | Legacy Language Codes | Jul 1 |
BenB wrote:
........, but either way it appears to be a bug. |
|
Hi all,
This is an interesting one, and I wanted to post because I don't think I would class this as a bug, but it would make an interesting feature request on ideas.sdl.com.
In some cases the language codes used by .Net applications (such as Studio) are incompatible and will not be recognized when the file is imported into older applications. One of these cases is nb-NO (Norwegian Bokmal) where Workbench uses the legacy language code no-NO, as Bjørnar discovered.
We have introduced a mapping from legacy codes to those used by Studio, but not the other way around as it would require corresponding "export modes" which then would apply the legacy (target) application's codes. However the target application may not be known at the time of export.
As a workaround you could attempt to import the bilingual files (ttx or itd) instead, if they were available, or edit the export file as Bjørnar has done. This type of thing is often a problem when looking at backwards migration because legacy applications don't always have the ability to use newer formats, handle custom field values or retain formatting for example).
Regards
Paul
SDL Support
  | | | |
Track this topic 
