Since the latest AMOS improvments, by default you automatically make your translation on the latest existing versions of each plugin/component, which is really useful.
Another useful thing is the ability to import a zip file, containing translations for several components.
But when you import such a zip file, you have to select the concerned Moodle version. And if you include files related to plugins not compatible with this version, they are ignored
Would it be possible that the import zip file tool could handle files for several versions, as the AMOS translation tool does?
It could be helpful (and avoid risk of thinking you have made a translation, but it has not been integrated).
To be precise, and coherent with AMOS editing, default should be to apply to latest versions ; and you could still select a precise Moodle version if you really want to.
I see that AMOS has been updated, with new 3.8 version (replacing Dev), and the same when importing from a file.
I come back to see if my suggestion about having same behaviour than AMOS manual use could be added when importing from a zip file : strings would be added to latest existing plugin versions (and not one specified version).
That would be very helpfull : i've made several big review/updates in french language pack, and it's really a pain to have to make it in (sometimes) more than 10 occurrences to accomodate each versions And for each big review i make. For exemple, i've made contrib 30711 to 30721, 30757 to 30765 and 30919 to 30930.
Having this aibility would really ease the process of having good translations, with coherence between core and plugins, for old and new plugins. Because i ended up not updating some (old) plugins, and i still have other changes to make, and don't want to again loose time to accomodate each version individually.
Do i need to create a specific tracker issue for that?