Translating via staff client causes problems at upgrade time

[Pasi Kallinen]

*EG master

Some strings, such as the names of the OUs, can be translated directly via the staff client. These translated texts go in the config.i18n_core table, and nothing separates them from strings that were put there during EG install. When you upgrade, you also need to put the updated strings from EG into that table, possibly overwriting the strings that were translated directly via staff client.

For example, if you just rename the "Example Consortium", and then upgrade EG, your consortium will be called "Example Consortium" once again...

I think there should be a boolean field which tells whether the entry comes from EG, or is a translation done via staff client. When the translations are looked up in the database, EG should prefer the translation done via staff client, and only use the EG stock translation iff the user supplied one doesn't exist.

[Thomas Berezansky (tsbere)]

I think the solution should actually be "don't provide translations for strings we *expect* you to edit". Allow translations of them, but don't provide core translations.

As far as I know this would merely mean removing the oils_i18n_gettext wrappers around the example org tree names and any other similar strings where we are anticipating edits to be made in the seed data.

[Ben Shum (bshum)]

Needs further discussion on approaches.