Changes both in translation and original model versions

[ncri]

Changes both in translation and original model versions

[shioyama]

Handling versions of attributes on both the translation and base model is an unsolved problem, unfortunately. At the moment globalize-versioning really is only made to handle versions of translations independent of versions on the base model. If you'd like to submit a PR to change this, please do, in the meantime I'm closing this.

[ncri]

Okay. Maybe ideally only the base model version should be kept, to not store duplicate info and to simplify things.

[shioyama]

It's not that simple, because translations are in a different table. paper_trail doesn't handle tracking versions from different tables (AFAICT). So unless you want to store your translations in the base table (using another translation gem), I don't see how to accomplish this in a simple way.

[ncri]

Yeah, I understand. I never wrote it is simple. I was just thinking what could be a more optimal solution in theory... And the odd thing is, as far as I remember, even without using globalize-versioning translation table changes are stored in the versions for the base table. So actually this might already work... I might do some tests...