[openstreetmap/openstreetmap-website] Add translation migration health check (PR #6836)
mmd
notifications at github.com
Tue Feb 24 22:27:31 UTC 2026
mmd-osm left a comment (openstreetmap/openstreetmap-website#6836)
I'm wondering if we could use a multi step process. Instead of renaming keys in a single commit, we could:
* Create additional i18n keys under their new name ahead of time
* Let Translatewiki do the translation for the new keys
* Merge the updated translations back into this repo
* Switch the code to use the new translation
* Remove the old i18n keys
I have no idea if this is feasible at all, in particular how much extra effort is involved on translatewiki side. It would prevent stale translations, though it introduces a bit more complexity to properly manage i18n key transition over time.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6836#issuecomment-3955092149
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/pull/6836/c3955092149 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260224/8bfc424b/attachment.htm>
More information about the rails-dev
mailing list