You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
under 'Automatic translation mode', select 'Add as "needing edit"'
under 'Search filter', select 'Untranslated strings'
under 'Source of automated translations', select 'Machine translation'
under 'Machine translation engines', select 'Microsoft Translator'
Other options are available and could be explored. By selecting 'Add as "needing edit"', the autotranslated strings would be treated as "fuzzy" translations, i.e. they would be added to the component source files when a patch is made, but they would NOT be used. My rationale is that a translator should review the translations, edit as necessary and uncheck "needing edit". Possibly teams using a dedicated review process (where strings require approval) can add select 'Add as translation', but this would need to be carefully checked, e.g. on a component with few untranslated strings.
Microsoft Translator is preferred for bulk translation as our free tier covers 2 million characters/month. DeepL only allows 500k chars/month, so it may be better to save this for translating one string at a time, but it could be tried if Microsoft Translator is much worse
The text was updated successfully, but these errors were encountered:
So far we have only been using machine translation to suggest translations when translating one string at a time.
It seems that its is possible to bulk translate a whole component:
Other options are available and could be explored. By selecting 'Add as "needing edit"', the autotranslated strings would be treated as "fuzzy" translations, i.e. they would be added to the component source files when a patch is made, but they would NOT be used. My rationale is that a translator should review the translations, edit as necessary and uncheck "needing edit". Possibly teams using a dedicated review process (where strings require approval) can add select 'Add as translation', but this would need to be carefully checked, e.g. on a component with few untranslated strings.
Microsoft Translator is preferred for bulk translation as our free tier covers 2 million characters/month. DeepL only allows 500k chars/month, so it may be better to save this for translating one string at a time, but it could be tried if Microsoft Translator is much worse
The text was updated successfully, but these errors were encountered: