Skip to content

docs: document the minimum translation memory threshold - #432

Open
lawl-dev wants to merge 2 commits into
mainfrom
docs/translation-memory-threshold-minimum
Open

lawl-dev wants to merge 2 commits into
mainfrom
docs/translation-memory-threshold-minimum

Conversation

@lawl-dev

@lawl-dev lawl-dev commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Both text and document translation treat a translation_memory_threshold below 50 as 50. Below that value no translation memory segment was applied, and 0 disabled the memory entirely, which was not documented.

  • openapi.yaml: note the behavior on the TranslationMemoryThreshold schema, and regenerate openapi.json
  • Translation memories guide: state the lowest supported threshold in the section on tuning it

The accepted request range is unchanged, so minimum: 0 stays as is. Values below 50 are still accepted, they are just raised. Tightening minimum to 50 would make a generated client reject a request the API handles.

The note sits on the shared TranslationMemoryThreshold schema and needs no endpoint qualifier, since POST /v2/translate and POST /v2/document now behave the same way.

Please hold merging until the document translation change is live in production. The text translation half already is.

Text translation treats a translation_memory_threshold below 50 as 50.
The accepted request range is unchanged, so the schema still allows 0-100.

The note names POST /v2/translate because the schema is shared with
POST /v2/document, which passes the value through unchanged.
@mintlify

mintlify Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
deepl-c950b784 🟢 Ready View Preview Sep 11, 2026, 9:56 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

Document translation now raises a value below 50 to 50 as well, so the note on
the shared schema no longer needs to name a single endpoint.
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