Bug 13897 with bug 24262 refine our translation process for install files converting the old SQL files used in the installer for mandatory and optional data into YAML files and adding processing to allow centralised translation of those files alongside the rest of the translation project. It raises the question, however, of how we should deal with the same data during upgrades. Currently we add the American English values with standard SQL in an atomicupdate file (copied into updatedatabase at push time). I'm envisaging we may be able to do away with the atomicupdates for this type of data insertion during upgrade and replace it with a step inside updatedatabase that pulls the data, translations and all from the yaml files. Opening this bug to discus and attempt such an implementation.
That would require quite a lot of work (at least non trivial) IMO. I have checked the different entries for 20.11 and I don't think we would benefit much from having such features. I am removing the "candidate" tag but feel free to add it back if you are willing to work on it!
This would be especially useful for new notices for example.
*** This bug has been marked as a duplicate of bug 34994 ***
Oops sorry, I wanted to do the opposite…
*** Bug 34994 has been marked as a duplicate of this bug. ***
*** Bug 36737 has been marked as a duplicate of this bug. ***