Studio 2015, cannot add new terms to term base under English-US

Question

There is a problem with Studio 2015 when adding new terms to Term Base - English words are always added under English-UK instead of English-US, although the language pair was set to English-US. There is no such problem with my 2014 version. So I am forced to use my Studio 2014 instead of the new 2015 :( Can someone help me with this? Thanks!

Paul · Accepted Answer

Hi Shun, 
 I created a video, it's longer than I wanted but I stepped through the entire process to make it as clear as I could. Hopefully it'll be easy enough to follow. 
 
 Regards

Paul · Answer

Hi Shun Tong, 
 
This sounds very odd. Can you check your project is set up with the correct language settings?

Paul · Answer

Hi Shun, 
 
I can't see your images, only blank boxes, but perhaps you should check your termbase settings for the project. perhaps the index is set incorrectly so for en-US it says en-UK? Might just need resetting correctly.

Paul · Answer

Hi Shun, 
 
Thanks for sending me the files... I also had the same problem. It seems this is actually caused by a bug that has already been fixed in development. It should be released in the next cumulative update, CU02. I don't have the release date for this yet and I don't have a simple workaround, but hopefully it won't be too far off. 
 
If your termbases are simple, so just terms for example, then it is probably better to use a termbase without the language flavours for now. So one for en(GB) and another for en(US). Then when the project is finished you export to a spreadsheet and add the terms to an export of your normal termbase, but in the right language column. Then convert back to a termbase. 
 
These are additional steps, but quite straightforward with the Glossary Converter and if your termbases don't have a complicated structure. I can help you with this if you like? 
 
Regards

Paul · Answer

Hi Shun, 
 I was just reminded of a better solution for you perhaps. If you avoid putting duplicate terms into two different sublanguages but rather work with one English index and use a picklist attribute field at term level to indicate the sublanguage then you can still separate the sublanguages but will not encounter this problem. 
 You can see how to work with attributes here : 
 
 But again, I can help you with this if you like? 
 Regards

Paul · Answer

Hi Shun, 
 
You can also use attributes for general use. If you set up input models then it gets easier because you can select the input model you need for your project and the correct attribute will be applied automatically whenever you add a term. It's actually a very neat way to work, and then comes automatically with the ability to also use them for QA. 
 
If you send me a small example of exactly how your termbase is set up I'll create an example of how this could work in practice for you... or was the termbase you sent me exactly the way your real one is set up? If so I'll use that. 
 
Regards

Trados Studio > 1. Trados Studio

Studio 2015, cannot add new terms to term base under English-US