I sync translations via the GitHub integration, and on nearly every sync, AI pre-translation appends a stray trailing },{ to some of my translated strings. It’s stored as literal translation text, so it exports into my files and renders verbatim in the UI — a button ends up literally reading Save availability},{.
Examples — the same short key came back with the suffix in language after language:
// cs
"newParticipantFormSubmit": "Uložit dostupnost},{",
// da
"newParticipantFormSubmit": "Gem tilgængelighed},{",
// es
"newParticipantFormSubmit": "Guardar disponibilidad},{",
// nl
"newParticipantFormSubmit": "Beschikbaarheid opslaan},{",
Source is clean: "newParticipantFormSubmit": "Save availability".
The source strings are clean (no },{), e.g. "newParticipantFormSubmit": "Save availability".
The pattern is very consistent across syncs:
- The artifact is always a trailing suffix
},{, never mid-string. - It only lands on short/simple strings. Strings that already contain a complete
{placeholder}are consistently spared. - It’s not tied to any one key
- In one sync a single short key came back with the artifact in 6 of 6 languages.
One thing I noticed: },{ is exactly the delimiter that joins ICU plural branches, and my files do contain ICU MessageFormat plural strings like {count, plural, =0 {No attendees} one {1 attendee} other {# attendees}}. So it looks like the AI pre-translation might be bleeding that structural token from a plural string onto neighboring short segments in the same batch — but that’s just a guess.
Is this a known AI pre-translation behavior, and is there a way to stop it?