Introducing Amazon Translate Custom Terminology

> some customers tell us that when they use the service to translate company-authored content like product documentation, website strings, functional content, knowledge bases, and help pages

Generally, applying automatic translation to content like this seems to produce poor output, at least in my experience. Usually, I prefer running content through a translator myself instead of relying on the “translation” to broken English, without any supporting context in the source language, that is sometimes provided.

I wonder if this would be really good for expanding acronyms in a given context or for keeping proper nouns accurate. For instance "RDS" to "Relation Data Store". This is something that impacts systems ranging from Ruby on Rails plural to singular system (I forget what is used), you can define irregulars essentially.

It's nice that you can now do the same for the translation.

This may help conversation systems[1], especially within an organization.

[1] https://medium.com/capital-one-tech/eno-ai-eq-3d939a2f6a7b

I know some professional translators who specialize in cleaning up machine-generated translations so that they have that 'native speaker' quality (Yes, including DeepL). I doubt Amazon Translate will help that much, if the goal is to reduce the use of a native speaker to clean up the generated translation.

updated: looks like aws reintent happening.