Automatic localization for messages

[danielhers]

Currently messages are written as Hebrew strings hard-coded in the source code. They should be written in a .po file and translated.

[esegal]

Which i18n framework should be used? I saw https://pythonhosted.org/Flask-Babel/ for server side and http://l20n.org/ for client side. Do we have a preference?

[danielhers]

Flask-Babel looks good. I think it also works for the templates: http://stackoverflow.com/questions/9515156/flask-babel-how-to-use-translation-in-jinja-template-file

[esegal]

I started working on integrating Flask-Babel. I'll soon push the changes, and then we need to start translating everything to English.

[omerxx]

I think an English translation already exists, ask @galraij

[danielhers]

Right, for the fields but not the messages, I think. Both can be integrated into .po files.

On Fri, Sep 18, 2015, 18:42 Omer Hamerman notifications@github.com wrote:

I think an English translation already exists, ask @galraij https://github.com/galraij

— Reply to this email directly or view it on GitHub https://github.com/hasadna/anyway/issues/94#issuecomment-141486027.

[esegal]

To start, I've integrated Flask-Babel (https://github.com/hasadna/anyway/pull/438). This will allow replacing strings with gettext('Message') function, to get the translated message according to the current request's chosen locale.

[danielhers]

From #310, here is the translation file for the data fields: https://docs.google.com/spreadsheets/d/1TxRQukcLzfno8kG-6eH_XEMrcuk2h8PNJOmY5IZUEzg/edit?usp=sharing

[danielhers]

See #438 for instructions on how to write translations.

[danielhers]

Accident details field translations:

Anyway ACC code book translation into english.xlsx