Bibijana Rostohar Bijelić 

Im sorry for your experience as this is not how its intended.

See my screen print where, I have EN - FR terms already saved.
In the Editor View I have EN-DE project and I am asking for the DE term to be added using Add Quick Term.

By highlighting Source & Target Term with Add Quick Term I get the popup letting me know the source term exists and is about to be updated.
But see the end result. I have EN term, FR term and the newly added DE term

As this is not working for you as I expect, please check the Termbase Settings to ensure the langues are correctly mapped

Thank you

Lyds

Dear Lydia

Thank you for your reply.

The termbase only has EN and SR and the languages are correctly mapped. See screenshot below.

Any other ideas? Thanks.

Best

Bibijana

Hello Bibijana Rostohar Bijelić , Lydia Simplicio 

Do we have any new info regarding this issue? I just encountered the same thing today in Trados Studio 2022 SR2, same langauge combination.

Thanks  in advance.

Hi Dejan Hribar (cc Simon Bratina )

I tried to reproduce this on Studio 2022 SR2, but everything worked as expected:

(Please excuse my Serbian – it's what Google Translate produced…) I tried both the Add and the Quick Add options, and they all worked perfectly.

Is this systematic or occasional?

Daniel

Hi Daniel Hug 
I encountered this today for the first time on a client's computer (in Serbia, translating from Serbian LATN to English GB). I tried updating Trados Studio and MultiTerm first to the latest version. Did not help. I then tried on another project (English>German), it worked fine. I tried creating a completely fresh project with a fresh TB, created from scratch, containing just the EN and SR-latn languages, and I got the same result (both terms when added through Add new term or Quick add new term) are being added under English.

Dejan Hribar 

Baffling. I can reproduce that with 2022 SR2. Clearly a bug. Lydia Simplicio 

But there is a workaround. If you use sub-languages in your termbase (Serbian-Serbia and English-GB), adding terms works as expected. Hitch is that you have to do this when you create the termbase. You can create a termbase and import structure and terms from another termbase, though, so this looks quite feasible.

Thank you, Daniel Hug 

We'll use the workaround for now.

Strange thing is I've been working with Serbian LATN (and also CYRL) occasionally in the past, but I haven't noticed this issue yet. Maybe the bug was introduced fairly recently (somewhere within the 2022 releases)?

Hi Daniel Hug 
I just tested this in Studio 2021 SR2 and I could repro the same issue, so it's not isolated just to Studio 2022.

Dejan Hribar 

Good news: This bug does not exist in Trados 2024 CU1. I just set up a project, same as I did for 2022, and everything is working as expected.

Cc: Lydia Simplicio , Simon Bratina , Bibijana Rostohar Bijelić 

Hi,

As Daniel Hug  confirms above, this issue occurs in Studio 2022(and probably older versions of Studio as well) and it was addressed in Studio 2024. 

We will do a fix in Studio 2022 in an upcoming release, Tracking number for this is : CRQ-40168. 

Thank you

Lori 

Hi,

As Daniel Hug  confirms above, this issue occurs in Studio 2022(and probably older versions of Studio as well) and it was addressed in Studio 2024. 

We will do a fix in Studio 2022 in an upcoming release, Tracking number for this is : CRQ-40168. 

Thank you

Lori