New entry in Termbase CTRL+F2 or CTRL+SHIFT+F2 via Project View

Question

Hi, 
 
 when I mark a word in the source segment and in the target segment and wonna add it to the TB with the function Quick add to the termbase (CTRL+SHIFT+F2) it adds both words to the target langauge, then I have manually to add the source langauge (+new langauge), cut and delete one entry in the target langauge and copy it to the source langauge entry.

To get this:

Don't know what I have done wrong by creating the TM, because in the SDL Multiterm is everything fine, only in the Project view I have this problem. Have done the last available update for Studio and Multiterm, but it didn't solved this problem. 
 
 Best regards, 
 Luka

Paul · Accepted Answer

Thanks Luka Lukić 
 I probably wasn't very clear: 
 Paul said: Paul said: CRQ-18036 Adding terms from Studio for Serbian termbase will add both source and target term to the same language 
 This one is still unresolved. But if you use the correct languages it seems to work so I'm not sure this needs any work to solve the problem you have reported here. Probably not. 
 So, if I set up a termbase like this: 
 
 Then it works. 
 In practice this should not be needed as it means you are forced to use specific languages rather than just the main group, but in all honesty I don't think this is anything we will ever fix in MultiTerm because the effort is too great for a product that is this old. 
 If you use "SDL Language Cloud Terminology" you should find this works without any problems, and I believe you can also use the Excel Terminology Provider from the appstore which may be a good workaround if you don't have complex definitions for your termbases. 
 So you have three workarounds, one still using MultiTerm and two others. Hopefully this is going to help you?

Luka Lukić · Answer

Hi Paul, 
 the easiest way to explain it, is to check the option "Show sublanguages" by creating the TB. Thank you for the assistence.

Paul · Answer

Luka Lukić 
 Two bugs confirmed and logged with the development team: 
 CRQ-18036 Adding terms from Studio for Serbian termbase will add both source and target term to the same language 
 CRQ-18037 Term recognition does not find terms from Serbian termbase 
 I can't give you timescales for the fix but it will be resolved in a future update.

Paul · Answer

Luka Lukić 
 Paul said: CRQ-18037 Term recognition does not find terms from Serbian termbase 
 The development team have done some good research on this one and have concluded that this isn't actually a bug in Studio/MultiTerm. I tested this again this morning and can confirm that I can now make this work. I'll give you the full explanation: 
 =========================== 
 The example uses Serbian (Latin, Bosnia and Herzegovina) but if you look at the text you will notice it is Cyrillic, not Latin. Unlike our Cloud-Based Terminology, which is probably unicode throughout, MultiTerm still converts text using windows code pages - 1250 for the Serbian Latin and 1251 for Cyrillic. 
 Term recognition works as expected using Serbian (Cyrillic, Bosnia and Herzegovina) for the document and termbase. 
 
 ============================= 
 In your example you are also using Latin and not Cyrillic. I don't know how we missed this the first time! 
 Paul said: CRQ-18036 Adding terms from Studio for Serbian termbase will add both source and target term to the same language 
 This one is still unresolved. But if you use the correct languages it seems to work so I'm not sure this needs any work to solve the problem you have reported here. Probably not.

Trados Studio > 1. Trados Studio

New entry in Termbase CTRL+F2 or CTRL+SHIFT+F2 via Project View

Top Replies