@AlainT,
There's a couple of things to unpack there,
If there's any Quebecois terms that you are correcting, if they completely incorrect / wrong etc, please could you raise a case for them (you can raise it as a single case), please include the URL path as to where that string is so our Localization team can review the context as well as the reasons you feel they aren't accurate / correct.
Secondly, the logic for the language packs during an upgrade (it's actually immediately after the upgrade has finished) is a little different to standard plugins. In that, for each of the 5 translation tables we have to do very specific checks (per translation). With regards to the entries in the [sys_documentation] table we are looking to see if that table's field label exists in the [sys_update_xml] table which would imply it is a customization. This then lets us know if we should ignore it.
Therefore the best way to migrate translations of this type between a sub-PROD instance and a PROD instance is indeed via update-sets, because if you run a manual import per instance it wouldn't necessarily add an entry in the [sys_update_xml] table. Ultimately the intention is always to ignore any changes you've made to what we provide ootb as you may have very valid reasons to change terms. We also would have no reason to touch / modify any net-new translations you've made due to the previously mentioned logic,
If you have any more questions on this specific topic, please feel free to reach out to me and we can organise a call if necessary,
Many thanks,
kind regards
--------------------------------------------------------------------
Director of Globalization Deployment, Internationalization
