Repository navigation
docs: glossaries without source_lang on /v2/translate - #478
Merged
Merged
Conversation
Text translation accepts glossary_id or glossary_ids without source_lang. DeepL detects the source language and applies the glossary's dictionary for the detected language pair. Document translation still requires source_lang with a glossary. - managing-glossaries: new "Use a glossary without a source language" section with a request and response, the 400 when the detected pair has no dictionary, short-text detection, and using one multilingual glossary - openapi.yaml: update glossary_id and glossary_ids on /v2/translate and the Glossaries tag description; document the 400 for a missing source_lang on the /v2/document glossary_id - document-translations, glossaries-in-the-real-world: align wording - changelog: October 28 entry - openapi.json regenerated from the YAML 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
- managing-glossaries: rename the section to "Use a glossary with automatic source language detection", state the REST-only, client library and document limits up front instead of in a trailing note, and turn the caveats into a troubleshooting list - state the example's assumption about the glossary entry so it no longer conflicts with the earlier example on the page - openapi.yaml: describe the glossary_id requirement as a dictionary for the language pair of the request (correct for multilingual glossaries), scope the Glossaries tag sentence to documents with a glossary, and document the 400 for glossary_ids on /v2/document - changelog: trim the entry to three bullets and link to the guide - update the anchor in the document translation and changelog links - openapi.json regenerated from the YAML 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
BriannaDelgado
approved these changes
Oct 28, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
POST /v2/translateacceptsglossary_idorglossary_idswithoutsource_lang. DeepL detects the source language and applies the glossary's dictionary for the detected language pair. This PR removes the wording that says glossaries can't be used with source language detection and documents the new behavior.Document translation (
POST /v2/document) still requiressource_langwith a glossary, and the official client libraries still require it client-side, so the docs say so.Changes
docs/customize/managing-glossaries.mdx: new section "Use a glossary without a source language" with a request and response, the400when the detected pair has no dictionary, short-text detection, and using one multilingual glossary. The intro to "Use a glossary in a translation" now sayssource_langis required for/v2/documentand optional for/v2/translate.api-reference/openapi.yaml(and the generatedopenapi.json): update theglossary_idandglossary_idsdescriptions on/v2/translate, the Glossaries tag description, and the/v2/documentglossary_iddescription (documents the400whensource_langis omitted).docs/best-practices/document-translations.mdx,docs/customize/glossaries-in-the-real-world.mdx: align wording (the tutorial example uses the Python SDK, so it now says "with the SDKs").docs/resources/roadmap-and-release-notes.mdx: October 28 changelog entry.Verification
Checked against the live API:
glossary_idandglossary_idswithoutsource_langreturn200and apply the glossary.400(No dictionary found for language pair ...), also forglossary_idswhen any listed glossary lacks it.source_langthat doesn't match the glossary returns the same400.POST /v2/documentwithglossary_idand nosource_langreturns400.The example response in the new section is real output.
Not run:
mint broken-links --check-anchors(mintisn't installed here). The new anchor is#use-a-glossary-without-a-source-language, referenced from the changelog, the document translation page and the glossary page itself.🤖 Generated with Claude Code