Hi, so I have set up the 2 types of portals (basic and advanced), and they work well but when it comes to selecting a glossary it always says that there is no match. I have called the APIs from Postman and it works well (I list the glossaries and use them successfully for translation with REST calls), but for some reason the Hub won’t see the glossaries as matching, so the combo box stays disabled in the UI.
When I look at GCP Explorer Log there is nothing except when I make a REST call from Postman.
Since it works with the REST calls, I don’t see why it would not work in the Hub.
Any clues?
Hi @Ben999999999,
Welcome to Google Cloud Community!
It might be that there are stopwords in your glossary entry. Translation Hub’s glossary functionality excludes certain common words, known as stopwords, from translation consideration. This exclusion only applies if the glossary entry exactly matches a stopword. For instance, the glossary entry “when” would be ignored, but “when and what” would be translated.
You may refer to this documentation which provides lists of stopwords for each language that uses them.
Note that languages without stopwords are not included.
I hope the above information is helpful.
Hi @ruthseki ,
There is no stop words, and it works when I call it via Postman so I feel it should work when using it with the Hub.
Thanks for the reply!