Hello everybody,
I am having the same problem I had a month ago with language pairs even though the default is en-US to fr-CA. I have copied the TMX file into the Notepad and replaced each occurrence of fr-FR with fr-CA, but I can't remember how to import the TXT file back into Trados. Anybody can help?
Thank you!
I guess you could do what I just did and searched for your other post:
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
But is there a way to import the corrected TXT from the Notepad back into Trados? I am having this problem with more than one TM. I am getting en-CA instead of en-US and fr_FR instead of fr-CA and would like to merge the TMs.
ok - so you gave us a clue now:
would like to merge the TMs.
You have a TMX (not TXT... that's a different type of TM) so all you have to do is select your existing SDLTM in the Translation Maintenance View, then click on import and select your 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
Sorry, I was not clear enough... I exported the TMX from Trados and copied it into the Notepad, then I replaced all occurences of en-CA with en-US. Not that it's done, I don't know how to import the corrected copy in the Notepad (TXT) back into Trados. I downloaded Olifant and Workbench 3.0 and nothing worked. I was just trying to convert a TXT doc into a TMX doc.
ok - I think I see your problem(s):
Notepad++ is here: https://notepad-plus-plus.org/downloads/
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
Hi Paul and thanks for your patience!
I did the steps that you suggested (and made a written note of the process for next time). So here is what I encountered:
Trados Import function does not seem to accept TXT docs. So I added .TMT as the extention and it worked.
That's because the file you are importing is a TMX and not a TXT. As I said, yours is a TXT because you called it that. A bit like me calling an XSLX a TXT... not the same things at all. A TXT in terms of a Translation Memory is a very specific type of Translation Memory. The old Trados pre-"Trados Studio" days used to support a TXT translation memory. Looks a bit like this:
Translate
<TWBExportFile version="7.0" generator="TW4Win" build="8.3.0.863">
<RTF Preamble>
<FontTable>
{\fonttbl
{\f1 \fmodern\fprq1 \fcharset0 Courier New;}
{\f2 \fswiss\fprq2 \fcharset0 Arial;}}
<StyleSheet>
{\stylesheet
{\St \s0 {\StN Normal}}
{\St \cs1 {\StB \v\f1\fs24\sub\cf12 }{\StN tw4winMark}}
{\St \cs2 {\StB \cf4\fs40\f1 }{\StN tw4winError}}
{\St \cs3 {\StB \f1\cf11\lang1024 }{\StN tw4winPopup}}
{\St \cs4 {\StB \f1\cf10\lang1024 }{\StN tw4winJump}}
{\St \cs5 {\StB \f1\cf15\lang1024 }{\StN tw4winExternal}}
{\St \cs6 {\StB \f1\cf6\lang1024 }{\StN tw4winInternal}}
{\St \cs7 {\StB \cf2 }{\StN tw4winTerm}}
{\St \cs8 {\StB \f1\cf13\lang1024 }{\StN DO_NOT_TRANSLATE}}}
</RTF Preamble>
<TrU>
<CrD>01062011, 18:28:59
<CrU>GLOBAL\pfilkin
<ChD>01062011, 18:28:59
<ChU>GLOBAL\pfilkin
<Seg L=EN-US>Uh.
<Seg L=DE-DE>Uh.
</TrU>
<TrU>
<CrD>01062011, 18:28:59
<CrU>GLOBAL\pfilkin
<ChD>01062011, 18:28:59
<ChU>GLOBAL\pfilkin
<Seg L=EN-US>JUDITH:
<Seg L=DE-DE>JUDITH:
</TrU>
<TrU>
<CrD>01062011, 18:28:59
<CrU>GLOBAL\pfilkin
<ChD>01062011, 18:28:59
<ChU>GLOBAL\pfilkin
<Seg L=EN-US>PILATE:
<Seg L=DE-DE>Pilatus:
</TrU>
<TrU>
<CrD>01062011, 18:28:59
<CrU>GLOBAL\pfilkin
<ChD>01062011, 18:28:59
<ChU>GLOBAL\pfilkin
<Seg L=EN-US>All wight.
<Seg L=DE-DE>Alle Wight.
</TrU>
<TrU>
<CrD>01062011, 18:28:59
<CrU>GLOBAL\pfilkin
<ChD>01062011, 18:28:59
<ChU>GLOBAL\pfilkin
<Seg L=EN-US>I will give you one more chance.
<Seg L=DE-DE>Ich gebe Ihnen noch eine Chance.
</TrU>
So if you have a TMX, and call it a TXT, you cannot expect Studio to import it.
Even though I found and replaced all en-CA occurrence with en-US, the TM was still labelled en-CA when I tried to merge it with the TM labelled en-US. I gave up understanding this part...
I don't understand what you mean either. What do you mean by labelled? Maybe show us the TM settings so we can see the languages in each one and we might be able to explain to you what you have done.
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, I meant "named" instead of labelled. It's just that when I try to merge the en-US TM with the en-CA TM (it's the same client), the updating tool merges only TMs that have the same language pair.
I tried to change the default language pair from en-CA to en-US by personalizing the variable and deleting en-CA, but en-CA won't go away!
Here are some screen grabs. I tried to send you TMX file in question, but the file type is not allowed
.
Sorry, I meant "named" instead of labelled. It's just that when I try to merge the en-US TM with the en-CA TM (it's the same client), the updating tool merges only TMs that have the same language pair.
I tried to change the default language pair from en-CA to en-US by personalizing the variable and deleting en-CA, but en-CA won't go away!
Here are some screen grabs. I tried to send you TMX file in question, but the file type is not allowed.