Translation functionality for translators

[ronaldtse]

In ISO TC 211 there will soon be a new release of terminology that involves many new and changed terms/definitions.

(https://github.com/geolexica/isotc211.geolexica.org/issues/75#issuecomment-639244906)

The translators will be using Glossarist to translate all of these newly released items:

• A translator for language X will want to look at new entries that do not have an X translation
  • The translator needs to view the English entry (and if the translator knows other translated languages, will want to check the translations of other languages)
• A translator for language X will want to look at updated entries to update the X translation
  • The translator will want to see the "translation from the previous version of this entry" for reference.
• A translation team may want to coordinate multiple translators, such as if there are 200 terms to translate, 4 translators can split into 50 each to translate. So they may want to see an overview of how many terms are not translated in language X, and see a list of those.

The Glossarist app should handle the above use cases.

[strogonoff]

@ronaldtse

A translation team may want to coordinate multiple translators

Currently, ensuring that no two people work on the same item is impossible without a third channel. This is equivalent to how it works with code—if I work on something specific, I would either have to message you about it or possibly deal with a merge conflict.

We could integrate such a channel if we were willing to run a real-time service for app instances to track what each user is looking at/working on. Any mechanism through Git would be too slow.

However, there are other ways at facilitating coordination, e.g. through the use of the upcoming collections feature (someone puts items into collections for each translator to go through).

[strogonoff]

Currently implemented (pending release):

• Filter showing only concepts which are missing translations to selected language
• Filter showing only concepts which have latest authoritative revision after latest selected language revision (i.e., concepts which have possibly outdated localized entries in selected language)
• Collection functionality, allowing to separate concepts into buckets for coordinated processing by translators

Already implemented:

• Compare selected language to authoritative language side by side
• Switch to another non-authoritative language (not side-by-side)
• Switch to previous revision of localized concept entry (not side-by-side)