| Vom Thema belegte Seiten: < [1 2 3] > | TBX file with Trados Initiator des Themas: Luca Ruella
|
|---|
pcovs
Dänemark
Local time: 20:08
Englisch > Dänisch
| Final suggestion | Mar 14, 2010 |
Have you tried then to add an extra extension saying .xml to your .tbx file?
I mean you should not delete anything of your file name nor of the .tbx extension, but you should add '.xml' and save this file.
What then?
| | | | | Still don't get it | Mar 14, 2010 |
Luca Ruella wrote:
I have a TBX file and this file needs to be translated. What part you do not understand?
I understand it at word level, it just doesn't make any sense without further explanation.
Why would anyone want you to translate a TBX file, that is, a glossary? Is it a bilingual glossary and your job is to expand it to 3 languages? Or is it a glossary with only one language filled in?
If they do want you to "translate a glossary", why would you want to import it to Multiterm? What will you do with it once it's imported?
The most sensible presumption was that you meant to say "open" or "import" the TBX, not translate it. Now I have no idea what's going on.
Luca Ruella wrote:
Nope. I have chosen the right radio button. In fact in the next screen Multiterm says "Please choose TBX file (*.xml)" and if I expand the file selection drop down menu, *.XML is the only possible selection that I am allowed to make.
Now, that is strange. Apologies for assuming it was your fault. It would seem that the TBX import in your Multiterm version doesn't work. Hopefully SDL support will come clean on this.
To the person who came up with the idea of making the file a .tbx.xml... while I applaud the spirit, I'm afraid that's not how computers work. Each file has one extension, the bit after the last dot. Everything before that (in this case, glossary.tbx) is simply part of the file name, so there is no practical difference between calling something glossary.tbx.xml or glossary.xml.
BTW the extension itself isn't too relevant, either. It's just to help programs and users identify the file type of each file, but it's not much more than a friendly indication, sort of "you may want to open this file with such and such program". If the Multiterm import window had an "All files" option apart from .xml like it should, the whole extension issue would be a moot point, and only the actual content of the file would matter. One could argue that this is the case as it is: MT Convert expects a (Multiterm-format) XML and even if you try to trick it by renaming your TBX to XML, all you get is an error message because the file format is not right. (Why it expects a Multiterm XML when the TBX option was selected is a mystery.)
| | | | Luca Ruella 
Vereinigte Staaten
Englisch > Italienisch
+ ...
THEMENSTARTER
Why would anyone want you to translate a TBX file, that is, a glossary?
Because you have a list of words in one language and you want them translated into another.
| | | | | Wrong approach | Mar 14, 2010 |
Luca Ruella wrote:
Why would anyone want you to translate a TBX file, that is, a glossary?
Because you have a list of words in one language and you want them translated into another.
In that case, you put (the client puts) the words in an Excel table or a txt file and translate them. Then the client can convert the term list to TBX, XML, relational database, morse code recorded onto vinyl records or whatever suits their fancy.
TBX is about the worst format for translating term lists, and, once this decidedly odd format was chosen, importing the TBX is about the worst way to go about the job.
Once you manage to import your TBX to Multiterm (which may or may not happen due to the peculiar way in which MultiTerm "works"), what will you do? Click through each entry, right click, pick the new language from the context menu (if it's there, God knows if it will be), click on the field and then type the term into the field? How much time will this take? What if you skip a term by accident?
Maybe I'm missing something and all this is perfectly normal somehow, but it seems to me that your client is awfully confused about formats and you didn't think hard enough about the technical aspects of the job to realise that.
If the TBX contains the tags for the target language terms you are supposed to add, you can just open the file in a text editor and type the terms between the tags. Alternatively, if you are allowed to or even supposed to overwrite the source language terms in the (monolingual) TBX, you may be able to process it with a CAT as if it were an XML file, which it basically is.
What I would do is contact the client first thing Monday morning and ask for a different source format (excel table, txt file) or an explanation.
Best of luck.
[Edited at 2010-03-15 08:32 GMT]
| | |
|
|
|
Selcuk Akyuz
Türkei
Local time: 21:08
Englisch > Türkisch
+ ...
| Why do you use Multiterm? | Mar 14, 2010 |
AFAIK, TBX files are XML files and you can translate them with any CAT tool. I tested a sample TBX file with Deja Vu X, Across and Transit XV, and all these programs were successful. I believe Trados TagEditor will be sufficient for this task.
[Edited at 2010-03-14 22:57 GMT]
| | | | | Again: What about changing the extension? | Mar 14, 2010 |
Luca Ruella wrote:
PCovs wrote:
You are sure you have browsed to the correct folder where you have saved your .tbx file, so you know it should be there?
I am very sorry if this is too silly, but I am really not getting why it will not find your file.
Yes I have tried that. It wont find my file because the only extension I can select (and therefore that can be displayed) is XML and my file is TBX.
Sorry for asking again but, don't you find it after changing the extension to TBX?
Daniel
| | | | | File extension relevant for filtering out files | Mar 14, 2010 |
FarkasAndras wrote:
To the person who came up with the idea of making the file a .tbx.xml... while I applaud the spirit, I'm afraid that's not how computers work. Each file has one extension, the bit after the last dot. Everything before that (in this case, glossary.tbx) is simply part of the file name, so there is no practical difference between calling something glossary.tbx.xml or glossary.xml.
BTW the extension itself isn't too relevant, either. It's just to help programs and users identify the file type of each file, but it's not much more than a friendly indication, sort of "you may want to open this file with such and such program". If the Multiterm import window had an "All files" option apart from .xml like it should, the whole extension issue would be a moot point, and only the actual content of the file would matter. One could argue that this is the case as it is: MT Convert expects a (Multiterm-format) XML and even if you try to trick it by renaming your TBX to XML, all you get is an error message because the file format is not right. (Why it expects a Multiterm XML when the TBX option was selected is a mystery.)
My impression is that the MultiTerm Convert is looking for a TBX file with the extension .XML.
MultiTerm must be filtering out files based on the extension and therefore not displaying files with the extension .TBX in the file open dialog.
Why do you think that MultiTerm is expecting a MultiTerm XML file and not a TBX file with the extension .XML?
Daniel
[Έγινε επεξεργασία στις 2010-03-14 23:31 GMT]
[Έγινε επεξεργασία στις 2010-03-14 23:52 GMT]
| | | | | But do you want to translate or add terms? | Mar 15, 2010 |
Selcuk Akyuz wrote:
AFAIK, TBX files are XML files and you can translate them with any CAT tool. I tested a sample TBX file with Deja Vu X, Across and Transit XV, and all these programs were successful. I believe Trados TagEditor will be sufficient for this task.
[Edited at 2010-03-14 22:57 GMT]
Hi, Selcuk,
How did you prepare the TBX file? Did you duplicate the source terms in the TBX file changing their language code? Otherwise, you would end up with a translated monolingual TBX file and not with a bilingual glossary, wouldn't you?
Daniel
| | |
|
|
|
Selcuk Akyuz
Türkei
Local time: 21:08
Englisch > Türkisch
+ ...
Daniel García wrote:
Hi, Selcuk,
How did you prepare the TBX file? Did you duplicate the source terms in the TBX file changing their language code? Otherwise, you would end up with a translated monolingual TBX file and not with a bilingual glossary, wouldn't you?
Daniel
It works if the file is already bilingual. But even in the other case, if the file is monolingual, a text editor like UltraEdit can be used to add target language codes.
| | | | | Because it's been tried already | Mar 15, 2010 |
Daniel García wrote:
FarkasAndras wrote:
To the person who came up with the idea of making the file a .tbx.xml... while I applaud the spirit, I'm afraid that's not how computers work. Each file has one extension, the bit after the last dot. Everything before that (in this case, glossary.tbx) is simply part of the file name, so there is no practical difference between calling something glossary.tbx.xml or glossary.xml.
BTW the extension itself isn't too relevant, either. It's just to help programs and users identify the file type of each file, but it's not much more than a friendly indication, sort of "you may want to open this file with such and such program". If the Multiterm import window had an "All files" option apart from .xml like it should, the whole extension issue would be a moot point, and only the actual content of the file would matter. One could argue that this is the case as it is: MT Convert expects a (Multiterm-format) XML and even if you try to trick it by renaming your TBX to XML, all you get is an error message because the file format is not right. (Why it expects a Multiterm XML when the TBX option was selected is a mystery.)
My impression is that the MultiTerm Convert is looking for a TBX file with the extension .XML.
MultiTerm must be filtering out files based on the extension and therefore not displaying files with the extension .TBX in the file open dialog.
Why do you think that MultiTerm is expecting a MultiTerm XML file and not a TBX file with the extension .XML?
Daniel
Yes on your first two paragraphs, it would seem like that at first sight. To the third: because it throws an error when the OP feeds in a TBX with an XML extension. By the way, let's not act like "TBX with an XML extension" is a normal thing. Something is obviously very wrong here.
Of course we're only going by what the OP claims, and as it turns out importing that file is not the priority anymore. Finding out what to do with it is.
| | | | | How to use MT Convert for this | Mar 15, 2010 |
Luca Ruella wrote:
thanks for your answer. however, if I select termbase exchange as source format in the third screen, convert asks me for an xml file, and I only have a tbx file. how do I convert it?
Hi Luca,
First of all, apologies for the really late response. I think I left you with some incomplete advice and then disappeared until now and can see you have had some ongoing problems ever since.
In case you have not managed to sort this out by now here's what you need to do (courtesy of Tracey who reminded me to complete this and gave me some good instructions).
First rename the tbx as .xml, or just add .xml to the end of the existing file. eg. abc.tbx.xml
The tbx file will reference a DTD and XSD file during conversion. If you don't have these you will find one of each in the MT Convert installation folder and it would make sense to place these into a folder with the tbx file.
- The DTD, TBXcdv04.dtd, is used to parse the document and distinguish between the tag elements and the text within the term entry.
- The XSD, TBXcsV02.xsd, is used to validate the TBX file before it is converted.
SDL MultiTerm Convert will use the DTD file to parse and distinguish the tag elements and actual text within the TBX XML file. The TBX XML contains the reference to the DTD file. In this way, SDL MultiTerm Convert can located the DTD and use it during the conversion. In most cases, the TBX XML references the DTD located within the same folder. However, some TBX XML files contain a static file path location, referencing the DTD in another location. So, to ensure that the DTD file can be referenced successfully during conversion, we recommend that you check the TBX XML and make any required edits. For example
Now you can go through your process to complete the conversion in MT Convert defining the field types to best represent the way you wish this to be displayed in MultiTerm. When you are finished there will be two files created;
- .mtf.xml – the converted terminology in SDL MultiTerm XML format, and,
- .xdt – the termbase definition file that can be used to create the new termbase in SDL MultiTerm.
Then use the *.xdt file to create a new termbase in SDL MultiTerm 2009. When the termbase has been created, browse to the Catalog view and import the *.mtf.xml. When the import is complete, the converted term entries will appear in the new termbase.
I hope this helps, but if you have any other questions please let me know.
Kind regards
Paul
[Edited at 2010-03-15 15:30 GMT]
| | | | | I am not sure of what Luca has done | Mar 15, 2010 |
FarkasAndras wrote:
Of course we're only going by what the OP claims, and as it turns out importing that file is not the priority anymore. Finding out what to do with it is.
From Luca's posts, it's not clear to me whether he renamed to .XML and then tried to convert using the TBX (which should work as per Paul's post) or whether he renamed from .TBX to .XML. That's why I kept asking Lucca.
It's a bit strange, however that there is not an option to show "All files" or at least files with the .TBX extension.
Daniel
| | |
|
|
|
pcovs
Dänemark
Local time: 20:08
Englisch > Dänisch
Daniel García wrote:
It's a bit strange, however that there is not an option to show "All files" or at least files with the .TBX extension.
Daniel
This is indeed strange, especially since the instructions from SDL Help say that there is no preparation of .tbx files before conversion! Go figure.
| | | |
SDL Support wrote:
First rename the tbx as .xml, or just add .xml to the end of the existing file. eg. abc.tbx.xml
The tbx file will reference a DTD and XSD file during conversion. If you don't have these you will find one of each in the MT Convert installation folder and it would make sense to place these into a folder with the tbx file.
- The DTD, TBXcdv04.dtd, is used to parse the document and distinguish between the tag elements and the text within the term entry.
- The XSD, TBXcsV02.xsd, is used to validate the TBX file before it is converted.
Can you tell us why the user has to jump through so many flaming hoops?
The fact that the software requires what is basically the wrong extension is just baffling, and the fact that whatever information the dtd and xsd files contain is not integrated into the software itself is embarrassing. It's not like each TBX needs a different user-provided dtd and xsd; this is supposed to be a standardised format that should be possible to import as is.
This really looks like the functionality was added as an afterthought, with hardly any consideration given to how it will be used and a good amount of lazyness thrown in for good measure.
| | | | Luca Ruella
Vereinigte Staaten
Englisch > Italienisch
+ ...
THEMENSTARTER | Way too complicated | Mar 17, 2010 |
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
| | | | | Vom Thema belegte Seiten: < [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 | Trados Business Manager Lite |
|---|
Create customer quotes and invoices from within Trados Studio
Trados Business Manager Lite helps to simplify and speed up some of the daily tasks, such as invoicing and reporting, associated with running your freelance translation business.
More info » |
| | LinguaCore |
|---|
AI Translation at Your Fingertips
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
Translation news related to SDL Trados
