Support localisation

[jlsjonas]

This is a feature request.

Description

Support localisation of tutorial (driver.js) steps

thoughts/options:

1. Handle it (mostly) within TutorialManager (/serverside)

   • cleaner manager structure (f.e. language tabs or sections in the form)
   • less wasted data (help is dynamically loaded, would add a lot of data to the translation json's
   • requires more significant data structure changes

2. Handle it like any other translation (using LocalisationManager)

   • reduced context/more risk of overlap (the same word might translate differently depending on context)
   • separated from tutorial manager (residing under localisation-> edit texts)
   • a lot of extra data in the translation strings .json that will most often not be needed
   • might require driver overrides/extra client-side load (currently tutorial fetches the page's steps & passes the server-side data almost directly to Driver)

I would argue that 1. is the best approach, but I'll leave that up for debate.

[aocneanu]

I would argue that 1. is the best approach, but I'll leave that up for debate.

The tutorials represent just another part of the same app. We have a localisation management system put in place, we should definitely use it instead of creating others.

[jlsjonas]

I hope you realize that, given the existing structure, this means all tutorial strings (which are usually a lot longer) will get transmitted double to client-side. This makes somewhat sense for the app itself, but for tutorials that have been imported dynamically (presumably to conserve bandwidth) this doesn't make much sense, imho.