Complete internationalization

[andreaskundig]

Internationalization was introduced as far as a particular client needed. I list the places I remember, but looking at it closely would probably reveal some other places.

For some parts of the application, we lack a translation mechanism:

• mechanism for multilingual consent forms
• mechanism to configure a translation for kepler (the component we use to display geographic maps)
• mechanism for multilingual /import page

Other parts can be implemented using existing mechanisms

• make home page multilingual
• Translate kepler to french #933 (given we have a mechanism for configuring kepler)

Finally there is some refactoring that would simplify the code but does not affect functionality

• Put all text in translation files (refactoring) #929

[andreaskundig]

I'm leaving this "for bizdev consideration" to see if any of the points has a high priority

[alexbfree]

Assigned to Charles for his input/consideration

[foucault-dumas]

I actually don't know how to answer to this.
As users go through all these steps (importing data, visualizing it, sharing it via the consent form), none is less urgent than the others.
As for the urgency of the whole thing vis-a-vis the rest, it seems to me that the need for translation is real for Uber drivers which is a more than current topic for us.