Improve localization schema

[selfbg]

Maybe instead of column per language (track.name_en, track.name_bg, etc) use another table with languages (id, name, code, ... ) and another one table for translations?

For example:

• Create one table Languages (lang_id, ....)
• In track table, remove name_bg and rename name_en to name.
• Create new table track_tr, with fk track_id, lang_id, translation

I think it will be better maintainable. @angelk Any thoughts?

[angelk]

How easy is to handle this using the current ORM - doctrine and symfony forms?

[selfbg]

@angelk You could see some initial ideas in the languages_schema branch.

I'm not sure how the forms will be handled.

• Maybe, there should be only one text field for name. On form submission, the controller check the current locale, and sets this field. However this way there won't be any fallback language.
• Force English name/description with optional translations.

[angelk]

The user should be able to fill multiple languages on single page.

May be this change will have more problems than improvements