Hi! We want our repetitions to be auto-propagated and confirmed by default to save time. However, we want linguists to have the option to change a single instance if the context requires it, without affecting the other repetitions.
Is there a setting to ensure auto-propagated strings arrive in a confirmed state, and how should linguists “isolate” a string if they need to edit it individually?
Hi @tetiana.rybachok !
In Project Settings → Import, you can enable the duplicate handling option Auto-translate duplicates. With this setting, when one string is translated, all identical strings (repetitions) are automatically populated with the same translation.
If a linguist needs to translate one repeated string differently due to context, they can simply edit that specific string manually in the Editor. Once a duplicate receives a unique translation, it becomes independent and no longer affects the other repetitions.
Let me know if I can help you further!
Hi! We have one more question regarding duplicate handling and approvals in Crowdin.
Our workflow looks like this:
We upload multiple files that contain identical strings (for example 5 files).
The strings get translated automatically or manually across all files.
Then a linguist reviews and approves translations, but only inside one “main” file.
The issue is that even if the same string already exists with identical translation in the other files, the approval status does not propagate automatically. As a result, linguists need to manually approve the same translation multiple times across duplicated files, which becomes very time-consuming on large localization projects.
Would it be possible to introduce functionality where:
approvals from one “main” duplicate string become the source of truth,
and the approved status automatically propagates to all identical duplicated strings/files, even if translations already existed there before?
This would significantly improve workflows!
Thank you!
Hi @tetiana.rybachok !
At the moment, Crowdin’s duplicate handling can automatically propagate translations across identical strings when the Auto-translate duplicates option is enabled. However, the approval status is stored separately for each string.
As a possible workaround, you may consider using the Pre-translate feature with the option to apply translations from Translation Memory and mark them as approved automatically. This can help reduce the amount of manual approval work after files are uploaded or updated.
If any further clarification or help is needed, feel free to reply in this thread 