Skip to content

Conversation

@Korpyc
Copy link
Contributor

@Korpyc Korpyc commented Jan 6, 2026

Advanced Google Translate with glossary did not function correctly because the integration passed only the glossary name (ID) rather than the required full glossary resource path. This change ensures the full path is used, restoring correct glossary-based translations.

@Korpyc Korpyc requested a review from nijel as a code owner January 6, 2026 19:02
@nijel nijel requested a review from Copilot January 7, 2026 08:00
@nijel nijel added this to the 5.15.2 milestone Jan 7, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a bug in the Google Cloud Translation Advanced integration where glossary-based translations were failing because the code was passing only the glossary name (ID) instead of the required full resource path to the Google Cloud Translation API.

Key Changes:

  • Added proper conversion of glossary ID to full resource path before passing to the API
  • Added null check to handle cases where no glossary is available

@nijel nijel requested a review from AliceVisek as a code owner January 7, 2026 08:18
@nijel nijel self-assigned this Jan 7, 2026
@nijel nijel merged commit d12614c into WeblateOrg:main Jan 7, 2026
48 of 50 checks passed
@nijel
Copy link
Member

nijel commented Jan 7, 2026

Merged, thanks for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants