| Pages sur ce sujet: < [1 2 3] | TBX file with Trados Auteur du fil: Luca Ruella
|
|---|
| Try with Virtaal | Apr 5, 2010 |
Luca Ruella wrote:
I have a "glossary.tbx" file that needs to be translated.
I've tried to import it with Multiterm but the wizard asks me a XML file, which I do not have.
Thanks in advance for your help.
Luca
| | | | Samuel Murray 
Pays-Bas
Local time: 19:10
Membre (2006)
anglais vers afrikaans
+ ...
Christo Petkov wrote:
Luca Ruella wrote:
I have a "glossary.tbx" file that needs to be translated.
Try with Virtaal
Yes, Virtaal is an option, although Virtaal sometimes thinks that the source language is the target language, and in Virtaal you can only edit the target language text (not the source). And there is no option for reversing source/target in Virtaal. And... Virtaal does not display the term definitions. And... Virtaal may choke on the TBX files if they have byte order marks (fixable with Olifant).
| | | | Samuel Murray
Pays-Bas
Local time: 19:10
Membre (2006)
anglais vers afrikaans
+ ...
| File extension issue? | Jun 17, 2010 |
Luca Ruella wrote:
Thanks a lot for your kind support and detailed reply. However, this is far too complicated and requires too many intermediate passages. I think I'll give up managing TBX files with multiterm and use another tool.
Having read all the posts in this thread, I can't help but wonder if the problem isn't/wasn't that file extension display on Luca's computer was disabled, and when he tried to add "xml" as an extension, he was really just changing foo.tbx to foo.xml.tbx, which would explain why the program didn't pick up the "xml" files. Just speculting here...
| | | | julienwp (X)
France
Local time: 19:10
anglais vers français
| TBX translated in Studio 2009 | Jun 18, 2010 |
Luca Ruella wrote:
Dear Paul,
Thanks a lot for your kind support and detailed reply. However, this is far too complicated and requires too many intermediate passages. I think I'll give up managing TBX files with multiterm and use another tool.
Thanks anyway
Hi Luca,
If you want to process a TBX in Trados Studio 2009, you can simply create a new file filter (XML based).
1. Create the file filter (XML) and name it
2. Use your TBX as a template (don't use default XML settings here)
3. In the parser rules, set unwanted elements to 'Not translatable' (martifHeader, transacGrp and langSet)
4. Display only what you need to translate: add an XPath (set to Always translatable) to the parser rules as follows:
//*[@xml:lang="EN"]
Note: replace EN with whatever language should be translated
That's it!
I'm pretty sure this can be done in TagEditor too
[Edited at 2010-06-18 13:12 GMT]
| | |
|
|
|
| Not all fields import into MT termbase | Oct 2, 2010 |
SDL MultTerm 8.1 (Studio 2009)
After successfully jumping through all the hoops as described by Paul from SDL support in an earlier post I was able to import the tbx file ok. However, the tbx file contained definitions in addition to the terms and these were not imported. Anyone have an idea why the definitions might not be imported along with the rest.
I used the xdt file (as mentioned by Paul) for my Termbase that was created during the conversion of the tbx file into... See more SDL MultTerm 8.1 (Studio 2009)
After successfully jumping through all the hoops as described by Paul from SDL support in an earlier post I was able to import the tbx file ok. However, the tbx file contained definitions in addition to the terms and these were not imported. Anyone have an idea why the definitions might not be imported along with the rest.
I used the xdt file (as mentioned by Paul) for my Termbase that was created during the conversion of the tbx file into the xml MultiTerm Termbase format, so all the same fields should match up correctly. At least that is what I assume.
The tbx file that I wanted to import can be found here:
http://www.microsoft.com/Language/en-US/Terminology.aspx
It's a free microsoft glossary.
Does anyone have any ideas or suggestions as to how I can import the definitions, too.
PS. @SDL support: when is this file recognition problem going to be solved? This can't be considered a normal procedure for importing tbx files and it has been known for quite some time now. Is there a fix in the pipeline?
thx
[Edited at 2010-10-02 20:06 GMT] ▲ Collapse
| | | |
Jonathan Hopkins wrote:
Anyone have an idea why the definitions might not be imported along with the rest.
Either
1) Lazy programming by SDL, or
2) Someone at Microsoft failed to follow the tbx spec, or
3) You need to do something differently.
My money is on 1).
Jonathan Hopkins wrote:
I used the xdt file (as mentioned by Paul) for my Termbase that was created during the conversion of the tbx file into the xml MultiTerm Termbase format, so all the same fields should match up correctly. At least that is what I assume.
The tbx file that I wanted to import can be found here:
http://www.microsoft.com/Language/en-US/Terminology.aspx
It's a free microsoft glossary.
Does anyone have any ideas or suggestions as to how I can import the definitions, too.
PS. @SDL support: when is this file recognition problem going to be solved? This can't be considered a normal procedure for importing tbx files and it has been known for quite some time now. Is there a fix in the pipeline?
I'm about to import the TBXes in my own languages, so I was about to look into this too. The easiest way is probably to convert the TBX to a spreadsheet... it's horrendous that we have to do this, as TBX was invented as a better alternative to spreadsheets in the first place, but as long as people (*cough* SDL *cough*) fail to follow the standards, it's all we have.
I did the En-De, here it is: http://rapidshare.com/files/422760935/Microsoft_En-De.xls
BTW I think I saw on the SDL website that they fixed the preposterous import process, so with the most recent MT update, it should be Next>Next>Next>Finish... but I wouldn't hold my breath on the lost definitions issue.
[Edited at 2010-10-02 22:21 GMT]
| | | | | Thanks Farkas | Oct 3, 2010 |
FarkasAndras wrote:
I'm about to import the TBXes in my own languages, so I was about to look into this too. The easiest way is probably to convert the TBX to a spreadsheet... it's horrendous that we have to do this, as TBX was invented as a better alternative to spreadsheets in the first place, but as long as people (*cough* SDL *cough*) fail to follow the standards, it's all we have.
I did the En-De, here it is: http://rapidshare.com/files/422760935/Microsoft_En-De.xls
Hi Farkas,
would you mind sending me your xls file to my e-mail address? The file that you posted on rapidshare is apparently no longer available:
File nicht verfügbar
Folgende Datei ist nicht mehr verfügbar:
http://rapidshare.com/files/422760935/Microsoft_En-De.xls4226 KB
Das File unter dem obigen Link existiert leider nicht mehr. Das kann aus folgenden Gründen sein:
* Das File wurde vom Uploader gelöscht
* Das File war Illegal und wurde von unserer Abuse Abteilung gelöscht
* Der Link ist falsch
* Das File wurde von einem User mit kostenlosem Account geupploaded und kann deshalb nur 10x heruntergeladen werden ohne RapidPro.
My e-mail address is available from my profile page.
I also converted the tbx to an xml file, but I couldn't figure out how to get the definitions to allign properly. The best I could do was get the terms side by side.
BTW I think I saw on the SDL website that they fixed the preposterous import process, so with the most recent MT update, it should be Next>Next>Next>Finish... but I wouldn't hold my breath on the lost definitions issue.
[Edited at 2010-10-02 22:21 GMT]
That would be nice. But I certainly won't hold my breath either.
| | | | | Mediafire link | Oct 3, 2010 |
Jonathan Hopkins wrote:
would you mind sending me your xls file to my e-mail address? The file that you posted on rapidshare is apparently no longer available:
From my end, it looks like an overloaded Rapidshare server.
Either way, I popped it on Mediafire to keep it public:
http://www.mediafire.com/?9s8atod6fumnwds
TBX is XML as it is. Of course if you could convert it to MultiTerm XML, you could import it, but that's probably not going to happen. What I did is just use some smart search and replace to convert it to a tab delimited table, and convert the character references to literal characters.
[Edited at 2010-10-03 18:52 GMT]
| | |
|
|
|
| How to use the TBX for your case | Oct 4, 2010 |
FarkasAndras wrote:
Jonathan Hopkins wrote:
Anyone have an idea why the definitions might not be imported along with the rest.
Either
1) Lazy programming by SDL, or
2) Someone at Microsoft failed to follow the tbx spec, or
3) You need to do something differently.
My money is on 1).
Of course it could be any of these (we're all human), so I had a play today with the MSoft files and can get the definitions in. Here's what I did.
First I started SDL MultiTerm Convert 2009 and selected the TBX option;
Then I browsed to the folder where my TBX files were (I downloaded a few as they look interesting) and selected it. This populated the output file, termbase definition file and log file locations automatically;
I clicked on next and wait a little while as the first file I selected was a big one, so I chose a smaller one for this test (no patience). I then skipped the next window as I'm not interested in validating the input against a schema. This takes me to the Field Types and I accept the one presented;
The next window is the Entry Structure so I add the Definition Field to the Index level. I think there are only English definitions anyway from inspecting the TBX beforehand;
I click on next and then next again and 2,390 terms are converted;
I click next and the finish. This process has placed three files into my folder, the output file (*.mtf.xml) the definition file (*.xdt) and a log file (*.log).
Now I open SDL MultiTerm 2009 and create a new termbase which opens up a wizard. In step 1 I load the definition file I just created;
In step 2 I give my termbase a friendly name (MSoft Glossary) and then I next, next, next, finish the creation process. Now I go to the catalog tab in my new termbase and I right click on Import and select Process;
In step 2 of the wizard I select the *.mtf.xml file I created in SDL MultiTerm Convert and this populates the log file
I type e for exclusions to name the exclusion file in step 3 and tell it to bring in everything;
I click on next, next and the import begins. A few minutes later and it's complete with all 2390 entries imported;
I click on next, finish and am presented with this;
You can see the terms for English and Maltese and also the Definition against English only as this is all that was in the original TBX.
This looks ok, so maybe you can try this method?
Regards
Paul
| | | | | Thanks to Farkas and Paul | Oct 4, 2010 |
Hi Paul,
I went through all those steps (after adding the xlm file extension to the tbx file), but the definitions weren't imported for me. However, after having gone through all the steps once again for the xls file that Farkas so generously provided, it worked fine. Since you were able to import the definitions straight from the tbx file, I'll just assume that I made a mistake in the structure setup pane (I believe that I added the definition as a sub-field of the Term, if memory ... See more Hi Paul,
I went through all those steps (after adding the xlm file extension to the tbx file), but the definitions weren't imported for me. However, after having gone through all the steps once again for the xls file that Farkas so generously provided, it worked fine. Since you were able to import the definitions straight from the tbx file, I'll just assume that I made a mistake in the structure setup pane (I believe that I added the definition as a sub-field of the Term, if memory serves well), though I can't see why that would cause any problems. Yours seems to appear at the same level as the term itself.
By the way, did you have to change/add the xlm file extension as you described in your earlier post? Or has that problem been indeed fixed now, so that you can actually see the tbx files for selection?
Cheers,
Jon
[Edited at 2010-10-04 20:19 GMT] ▲ Collapse
| | | | | only irregularities to report from me when importing tbx | Oct 4, 2010 |
SDL Support wrote:
I click on next, next and the import begins. A few minutes later and it's complete with all 2390 entries imported;
Unfortunately for me, I just get irregularities when I try to import directly from the tbx files (and I still had to add the file extension .xml first, before converting):
@Paul: did you try importing several languages into the same termbase, clicking on the synchronisation option?
I have no idea why this isn't working for me. All your screenshots look the same to me when I complete the process.
| | | | | You are placing the definition in the wrong place | Oct 4, 2010 |
Jonathan Hopkins wrote:
Since you were able to import the definitions straight from the tbx file, I'll just assume that I made a mistake in the structure setup pane (I believe that I added the definition as a sub-field of the Term, if memory serves well), though I can't see why that would cause any problems. Yours seems to appear at the same level as the term itself.
Hi, Jonathan,
I think that is precisely the problem.
In the Microsoft TBX files that I have seen the definition is inserted at language level:
EN
Definition
Term
Term
ES
Term
Term
In your convertion, you specified that the definition field should be under the "Term":
EN
Term
Definition
Term
Definition
ES
Term
Term
It seems that MultiTerm is ignoring the EN/Definition field in the TBX because you are telling it to look for an EN/Term/Definition field.
In Microsofot's TBX, the definition is the same for all synonyms.
In your custom definition, each synonym could have a different definition.
MultiTerm is not moving the definition from the language level to the term level (I guess it would not know into which synonym to attach the definition).
What can you do?
You can keep the definition at language level as it is in the Microsoft file (what Paul did).
Or, if you really want to have the definition at term level, you would need to move in the TBX file before converting it. The only thing is that, if you do it, you will have to think if you want the definition automatically transferred to the first synonym or to the second or to both.
If there are not so many definitions, you might want to import into MultiTerm keeping Microsoft's structure and then move the definitions manually.
I hope this helps!
Daniel
| | |
|
|
|
Jonathan Hopkins wrote:
By the way, did you have to change/add the xlm file extension as you described in your earlier post? Or has that problem been indeed fixed now, so that you can actually see the tbx files for selection?
Cheers,
Jon
Hi Jon,
To be honest this is one of the fixes in SP3. I didn't even think about it until you mentioned it and the development team confirmed for me. You no longer have to workaround the way we did previously and you can select the TBX as you should be able to. SP3 should be released this week.
This import still worked for us with SP2 using the workaround described earlier, we tested in Support to make sure. I think Daniel is correct in that part of your problem is down to the way MSoft intend the structure to be and if you use their definition you must follow it. I believe best practice here is as MSoft have done it with the definition at language level. When you place it where you did on the Term it is fine for simple glossaries but if you add synonyms then in theory you should add a definition to each one which is just increased and unnecessary work..... although maybe this is a purist view (not mine) and really not that important for your usecase?
Regards
Paul
| | | | | Definition at index level did the trick | Oct 5, 2010 |
I can confirm that this was indeed the problem. I re-imported the glossary with the definition at index level and everything worked fine as in Paul's example above.
Thanks to everyone who contributed.
...now, back to work...
Cheers
| | | | Selcuk Akyuz
Turquie
Local time: 20:10
anglais vers turc
+ ...
| Much easier with Across | Oct 25, 2010 |
I don't like Across as a CAT tool but it easily imported the file with all the synonyms and definitions. No need for any settings, just import!
| | | | | Pages sur ce sujet: < [1 2 3] | To report site rules violations or get help, contact a site moderator: You can also contact site staff by submitting a support request » TBX file with Trados | Anycount & Translation Office 3000 | Translation Office 3000
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.
More info » |
| | TM-Town | Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
