Translation memory, terminology & review workflow — found from sitemap — Locize

Cited by

Facts read from this source

• Review queue types Report an error

  “Review in Locize is one queue with two kinds of entries: Proposals: a value that waits for a decision before it goes live.”

• Review proposals enablement Report an error

  “You enable review proposals for specific languages by navigating to your project settings page, in the "EDITOR, TM/MT/AI, ORDERING" tab and clicking the "Review proposals" row in the "Translation Quality" card.”

• Marked values trigger mt AI Report an error

  “machine translation or AI wrote it: automatic translation, the editor's suggestions, or a value pushed over the API with quality MT or AI,”

• Marked values trigger source change Report an error

  “the source text of an already translated key changes (setting Review on source change, on by default): every translation of that key gets marked, so translators see at a glance what to re-check,”

• Marked values API cli Report an error

  “your CLI or API push says so (needsReview: true, see below),”

• Marked values manual Report an error

  “someone marks it by hand in the editor: Mark needs review in the row's ACTIONS menu, or mark all in the bulk actions.”

• Confirm permissions Report an error

  “Confirming is a reviewer's action: an admin, a manager, or a user with the review permission for that language.”

• Review notification threshold Report an error

  “Needs review notify threshold: when the number of segments needing review in a language crosses this count, a needsReviewThreshold notification goes out (Slack, Microsoft Teams, webhook, GitHub dispatch), once per crossing.”

• Review notification plan Report an error

  “Needs a plan that includes notifications.”

• Mark machine translations setting Report an error

  “Mark machine translations: which machine and AI translations get the mark: always (the default), only when not confident (no quality-estimation score at or above the project's threshold; a translation without a score counts as not confident, so plain machine translation is marked), or never.”

• Cli needs review flag Report an error

  “locize sync --reference-language-only false --needs-review true Requires locize-cli 12.8.0 or newer.”

• API needs review Report an error

  “Send the value as an object with needsReview:”

• Gettext fuzzy mapping Report an error

  “The mark is the #, fuzzy flag of gettext. Fuzzy entries in a .po file arrive marked as needing review,”

• API review flag Report an error

  “Use ?review=true on the update endpoint to create a review proposal instead of a direct write:”

• API review constraints Report an error

  “review=true cannot be combined with the replace option, and the language has to have review proposals enabled.”

• Cli review flag Report an error

  “locize sync --reference-language-only false --review true Requires locize-cli 12.6.0 or newer.”

• Autotranslate review Report an error

  “When using the CLI, API, or MCP, automatic translations bypass review proposals by default. You can route them through review by adding autotranslatereview=true to your API call or CLI command.”

• Mcp auto translate review Report an error

  “The MCP server tools update_translations and report_missing_keys also support the autoTranslateReview parameter.”

• Review AI workflow Report an error

  “With Quality Estimation and its Review AI workflow setting, Locize additionally routes only low-confidence AI translations into review: selectively, across all languages, even those without the regular review workflow enabled.”

• AI review existing Report an error

  “AI Review checks the translations a project already has, whoever wrote them, and puts the doubted ones into this queue: a proposal with the suggested fix where the evaluator can improve the text, a mark where it cannot.”

• Provenance export Report an error

  “The provenance export packages this evidence as a CSV and JSON report per version, language or namespace: open the context menu in the project overview and choose provenance.”

• Provenance content Report an error

  “Every accept and decline is recorded in the segment history, including who decided, when, and (for AI proposals) the confidence score at decision time.”

• Article50 compatibility Report an error

  “For the full setup see Running an Article 50(4)-compatible review workflow.”

• Review health card Report an error

  “The project overview shows the size of the review queue per language, and the Health card shows the split into proposals and marked values.”

• Copyright holder Report an error

  “© 2026 inweso Ltd liab. Co. All Rights Reserved.”

Scores citing this record

• The App Developer Translation memory, terminology & review workflow
• The Data Protection Officer Translation memory, terminology & review workflow
• The In-House Document Translator Translation memory, terminology & review workflow
• The E-Commerce Marketer Translation memory, terminology & review workflow
• The Localization Manager Translation memory, terminology & review workflow
• The Skeptic Machine translation & AI quality
• The Skeptic Translation memory, terminology & review workflow