Multiple plugins introduce the concept of a glossary/thesaurus.

For consistency reasons, the site should globally define such a list: terms and their reference translation in other languages. The glossary is then sent attached to the jobs to make the translator follow the site standards.

This list might be initially created as a small set of words .. and it will be growing over time.
Since these words are not always used in their neutral form in text content, we cannot reduce the list to the words used only in a job.

Comments

miro_dietiker’s picture

Still trying to match intelligently (>80% word match?) would be awesome.
Users could additionally still add manually glossary items to the job by clicking them in.

For most cases, always sending the glossary wouldn't help... it would be simply too much and translators might ignore it.

miro_dietiker’s picture

miro_dietiker’s picture

Related #1891848: introduce translation memory

A glossary / thesaurus is formally already a translation memory. :-)

miro_dietiker’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes

Let's move dreams to 8.x