Weekly Release Notes

Weekly Release Notes — July 6, 2026

Content is machine translated from English by Phrase Language AI.

The release notes summarize the changes introduced over the previous week.

New Features & Improvements

  • Auto Adapt now enforces Term Base terminology when the content profile calls for it — terms are treated as hard constraints rather than soft suggestions, addressing cases where preferred terms were previously missed or misused
  • Strings Jobs Dashboard now loads each section independently in the background, eliminating waits of up to 10 seconds on large accounts
  • Strings Figma plugin Connect tab now offers case-insensitive content matching, an option to skip layers whose text matches multiple keys, and a post-action summary of connected and skipped layers
  • Strings job automations now offer the Upload Batch trigger
  • Strings automations table now shows a Job Template column with a quick-access link, and stays on the current page after an action instead of resetting to the first page
  • AITA is now selectable as a translation engine in Strings, both as an account-level default and as a per-language-pair override (for accounts with TMS)
  • Strings catalog now supports a locale code mapping format option (e.g. BCP 47 or custom naming)
  • Studio now supports voice cloning for multiple speakers from a single audio file, using speaker diarization to split and clone each voice
  • Studio share links can now be restricted to a single language, so reviewers only see and edit their assigned language
  • Studio admins can now edit pronunciation rules, subtitle profiles, and transcription glossaries created by any user in the organization
  • Studio voice preview now supports custom preview text, and lets you save favorite voices for quick access
  • Studio dubbing tracks can now be downloaded individually or all at once
  • Studio Reading Mode now groups segments by speaker and supports inline editing

Bug Fixes

  • Fixed: Contentful 2.0 connector failed to authorize when the EU data center was selected — EU-issued tokens were being sent to the US endpoint, causing an authorization error
  • Fixed: Sanity in-context preview was not working in the TMS editor
  • Fixed: Translation Memory search API returned an empty file when querying more than one language at a time
  • Fixed: TMS project status did not automatically change to Completed when several jobs completed within the same second
  • Fixed: "Analysis Created" webhook could be sent more than once for the same event
  • Fixed: A saved jobs view could return jobs that didn't match the saved filter criteria until a filter was manually adjusted
  • Fixed: Job editor could fail to load with an infinite loading screen after a source file update
  • Fixed: A corrupted saved sort preference could prevent the job list from loading at all
  • Fixed: Project managers without the "Modify global server settings" permission were unable to edit custom field values on existing jobs
  • Fixed: XLIFF 2.0 exports could drop structural tags, causing export failures
  • Fixed: The raw ASCII backspace character was silently dropped when importing .strings files
  • Fixed: Markdown export was not preserving asterisk and pipe character escaping present in the source
  • Fixed: Machine translation suggestions for right-to-left languages displayed in the wrong word order in the Strings editor
  • Fixed: Strings locale view showed an inflated untranslated key count that didn't match the editor
  • Fixed: Studio CJK punctuation processing corrupted clause-final punctuation and ellipses
  • Fixed: Studio "Send to TMS" failed when a target language code exceeded six characters
  • Fixed: Studio dubbing preview had choppy audio playback after translating subtitles
  • Fixed: Studio dubbing changes could get stuck in a generating state after switching dubbing provider
  • Fixed: XML in-context preview could lose content from some columns when joined jobs were filtered in the CAT editor
Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.