Cloud translation doesn't use glossary in glossary config

Hello everyone,

Our team has been using the Cloud Translation service to translate strings from Chinese into other languages, with the help of glossaries. However, we have recently encountered an issue where we are unable to use newly uploaded glossaries to perform translations.

Problem Details

  • The issue began on December 22nd, 2022.
  • We have attempted to upload the last available glossary again to prove that the issue is not with the format or the validity of the glossary.
  • We have also tried updating the glossary with a new entry, but this did not resolve the problem.
  • However, we have tested with an older glossary, which worked fine. Therefore, we suspect that the issue is not with the API itself.

Request for Assistance

Despite searching through the documentation, we have not been able to find any helpful information to resolve this issue. We are seeking advice and guidance from the community to determine what could be causing this problem and how we can address it.

Thank you for your help in advance.

1 Like

Hi @Will_Chang ,

Welcome to Google Cloud Community.

It’s likely that the Cloud Translation API service may be having problems. I advise monitoring the Cloud Translation API status page to see if any service interruptions or outages have been recorded that might be affecting the API’s capacity to handle recently submitted glossaries. You may want to check the Cloud Translation API documentation to see if the glossary format you’re using is supported by the API.

Here are some documentation that might help you:
https://cloud.google.com/translate/docs/reference/rpc?_ga=2.179633764.-1392753435.1676655686
https://cloud.google.com/translate/docs/advanced/glossary?_ga=2.179633764.-1392753435.1676655686
https://cloud.google.com/translation-hub/docs/admin-glossary?_ga=2.179633764.-1392753435.1676655686

1 Like

Hi @Aris_O ,

Thanks for your information.

I have gone through all the documentation you provided and tried some additional steps.

  • List all the glossaries under our project to ensure that the target glossary exists.
  • Go to the Translation Hub > Resource > Glossaries and verified that the target glossary was present.
  • List all the entries under target glossary and everything seemed to be in order.

Then I trying to call translate API with the payload below

{
   "targetLanguageCode":"en",
   "sourceLanguageCode":"zh_TW",
   "mimeType":"text/plain",
   "glossaryConfig":{
      "glossary":"target_glossary",
      "ignoreCase":true
   },
   "contents":[
      "測試"
   ]
}

The response be like:

{
    "translations": [
        {
            "translatedText": "test"
        }
    ],
    "glossaryTranslations": [
        {}
    ]
}

Translation API is not using target glossary to translate. Do you have any idea about this problem?