Multi-language support

[blixhavn]

We need the pages module to be multi-language, where one URL shows content based on selected language, or redirects to the corresponding URL (i.e. [en] https://demo.tind.io/terms -> [de] https://demo.tind.io/bedingungen)

Is there any work being done on this, or have you discussed it?

[jirikuncar]

Proposal

http://sqlalchemy-utils.readthedocs.org/en/latest/internationalization.html

[blixhavn]

Invenio-pages is on MySQL for now. What do you think of introducing this with MySQL, and then migrating later, when Invenio is also moving to PostgreSQL? I'm pretty sure we'll have to create a MySQL fork otherwise. I'm of course also asking because TIND is currently on Invenio 2.0, and I don't see us migrating to 2.3 in quite a while.

More specifically I'm thinking of creating a kind of wrapper model/table that will work seamlessly with the TranslationHybrid class. Basically mocking key/value storage in regular relational database. This will be extra work for us, but at least it will allow us to move to PostgreSQL easily when the time comes.
Database migration might be a bit tricky though, but it should be doable.

[jirikuncar]

@blixhavn maybe you can use some less effective implementation of HSTORE in MySQL (e.g. db.JSON which is a TEXT column with json serialization).

[blixhavn]

Ah, that might work too. Great :)

[blixhavn]

Should we have a "master" value for url/title/content, or should we have everything as translations?

[blixhavn]

I've started looking into this now, but I am a bit stuck. In order to be able to implement this the way you suggested, we need to do some data handling in between the form/view and the model. How can we do this here?