Hi Jungyun Ok,

Please advise the latest versions of your Studio and Multiterm. To do that go to Help tab -up in the ribbon- then to About SDL Trados Studio/Multiterm. They should be both at the same update definition to ensure its optimum performance.

Besides, what happens if you copy the term  and paste it in the Search box? Does it get recognized? 

Does this happen to other termbases as well or only this one?

Hello, Oana. Thank you for your answer. The version of my Studio is 2019 SR2 - 15.2.5.2145 while that of my Multiterm is 2019 - 15.05.56289. Their versions differ but I believe both of them are up to date because no new available updates show up when I click Check for Updates in any of both programs. (Or if they are not actually up to date, please let me know other ways to update them.)  The problem persists with any termbase I use. 

If the desired term is, for instance, "비비고 왕교자," typing "비비고 왕교자" in the search bar yields a matching result, which of course is the term "비비고 왕교자." However, if I type in "왕교자," no results turn up, regardless of my hitlist settings. And this is problematic, because if the source text contains a term called "1% 나눔재단" but the actual matching term in my termbase is "포스코 1% 나눔재단," the term is not recognized. I didn't have this problem with Trados 2017. Thanks for reading and your attention. 

Regards,

Ok 

Jungyun Ok

I tested this in Studio 2017 and it's not working for me there either.  Are you sure this isn't related to the difficulties in tokenizing a language like Korean?  Can you show this working in Trados 2017?

Jungyun Ok

I tested this in Studio 2017 and it's not working for me there either.  Are you sure this isn't related to the difficulties in tokenizing a language like Korean?  Can you show this working in Trados 2017?

Hi, Paul. Unfortunately, I had to delete my copy of Trados 2017 because of its causing issues with my Trados 2019. For your information, after tinkering with my Trados 2019 (I did a couple of things for it so I am unsure of the exact cause), I witnessed the function working properly (wow, how come?), but the next time I opened the Trados 2019, I found out the function had gone back to its normal dysfunctioning state.