• State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1292 views
  • Users 0 members are here
Options
Related

Trado 2019 recognizes only the first two characters of a given term (hence terms not properly recognized)

Jungyun Ok

Hello, a Korean-English translator here.

Lately, I've been having problems with Trado 2019's termbase function. Well, I don't know... most probably the function hasn't been working properly since the get-go.

The terms in any of my termbases (Korean->English) are not properly recognized and, worse, even not searchable. For instance, if I manually search for a term called "나눔재단" by typing "나눔" in the search bar, the (matching English) term shows up in the results pane. However, if I type in "재단," no results turn up. The same goes for any other Korean-English term, whether there are spaces between the words or not.

My Trado 2019 and Multiterm 2019 are all up to date. I even tried this SDL fresh start app in a futile attempt to fix this problem. To be honest, the situation is very frustrating and annoying. What should I do? Thanks in advance for your answers. 

*

Here's a short video of me demonstrating the problem for your reference:

https://drive.google.com/open?id=1JjRkjAjBVIu4wjmQ0RFDFuh8rHI2Upkz
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Oana Nagy

    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 
  • 0 in reply to 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?

    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

  • 0 in reply to Paul

    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.