I am having trouble converting an existing glossary to a termbase using the Glossary Converter drag and drop app. Each time I drag the Excel file in, an error message comes up saying 'No languages have been defined: skipping file. Any tips on how to resolve this would be much appreciated!
How do you called the columns? I mean which language. The converter will not accept Polish for example. Or did you forget to put language names in the first cell?
_________________________________________________________
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.
Hi,
"Polish" should be ok... at least it is for me but if I add "Java" as a language it clearly is not recognised and I get this message window:
All I do now is select the language it should be, and I selected Bosnian (no reason... it was just where my mouse landed) and clicked on OK. This created by Polish, English, Bosnian termbase.
Maybe worth checking herein the settings file:
C:\Users\<username>\AppData\Local\AppData\Local\SDL OpenExchange\GlossaryConverter
I now have this in my file:
So you can see "java" is added and from now on it will be recognised... no "Polish" though ;-)
Regards
Paul
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,
"Polish" should be ok... at least it is for me but if I add "Java" as a language it clearly is not recognised and I get this message window:
All I do now is select the language it should be, and I selected Bosnian (no reason... it was just where my mouse landed) and clicked on OK. This created by Polish, English, Bosnian termbase.
Maybe worth checking herein the settings file:
C:\Users\<username>\AppData\Local\AppData\Local\SDL OpenExchange\GlossaryConverter
I now have this in my file:
So you can see "java" is added and from now on it will be recognised... no "Polish" though ;-)
Regards
Paul
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
"Polish" is ok, but I am afraid, "Polski" or "Węgierski" not anymore...
_________________________________________________________
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.
Hi Jerzy... no doubt. But presumably this is only the first time? I did a quick test and am asked the first time only, so once I have mapped the names all is well.
Regards
Paul
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
Most probably yes - I found the converter asking me for a language setting for a descriptive field.
So I assume it will convert languages-only Excel to MT, with no descriptive fields. How does it behave when converting MT to Excel, if the MT has had descriptive fields?
Many thanks and best regards, Jerzy
_________________________________________________________
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.
Hi Jerzy, you can take a termbase of any complexity and what you'll get back is the terms only. This is a simple tool designed to take the work out of something for the vast majority of translators who only need, or want, a simple glossary.
Cheers
Paul
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
Thanks for confirming :)
A great tool though, as most people I know would never use MT because of the (presumable) complexity in the process of creating termbases. MT if by far not that complicated, but when you see it for the first time, the wish to capitulate is stronger than the will to have a glossary.
Cheers, Jerzy
_________________________________________________________
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.
Translate
