The original content translation spec mentioned an interface where translators could see everything that needed translating on one page, but this doesn’t seem to have been implemented. 

The issue

There’s no way to know currently what needs to be translated. Course editors need to keep detailed notes in a spreadsheet. This is not a scalable approach to communicating updates. This may cause course content editors to update content sparingly, as they then need to send a detailed document outlining every update and where the updated content is located.

What we want

We want translators to be alerted when original (English-language in this case) text has been updated since the last translation in the translator’s current language was made.

1. A translator logs in.
2. Their language in Moodle is set to French.
3. We check the hash relationship table and see if a translation exists in the current language (French) for the new hash. If it does exist, an alert pops up showing the translations needing updating, with links to see the edit in context.#
4. Another way to access this translation admin tool is:
   1. Clicking Settings (frontpage/courses/other pages*) > ‘Turn translating on’ reveals another menu item ‘Translations manager’. Clicking ‘Translations manager’ launches a pop up modal showing a list of translations that need updating.
   2. The Translations needing updating can be relaunched with this second link in the settings (cog) menu below ‘Turn translating off’.

#If this modal is launched to alert translators to new content needing translation, 'Turn translating on' mode could be enabled automatically.

E.g. the Settings menu (with translating turned on) could contain:

• Turn editing on
• Edit settings
• Turn translating off
• Translation manager
• Filters
• Backup
• Restore
• More...

This is a screenshot of the settings menu referred to above:

• Ideally we also want to show new content needing translation. Andrew Lyons (Moodle HQ developer) suggests this should be easy enough to find, using the table and field list in the patch outlined in CONTRIB-8700. My only concern is how many strings this may result in. Could we manage this by pagination?

*See 'extend_navigation_frontpage' and 'extend_navigation_course' at https://docs.moodle.org/dev/Callbacks

Translations manager modal

The ‘Translations manager’ pop-up could look like this (notes in [...] don’t form part of the UI)

• Unchanged translations should appear at the bottom of the list.
• The language is taken from the current language selected in the Moodle language menu by default and if no translation exists for that language a parent language is loaded (where one exists) with a note "loaded from <language name>"
• You can delete an entry, once accepting a confirmation that you really want to delete. This sets the 'hidefromtable' field to 1, so can be undone in the database.
• Any 'hidefromtable' entries are not shown in the Translations Manager.

Current language: [French    v]                                                                                                                             [Save changes]
Show unchanged [disabled by default]

                                                  < 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 >                                                                                [Save changes]