[openstreetmap/openstreetmap-website] Best method for renaming translation keys? (#1289)

Andy Allan notifications at github.com
Thu Sep 15 10:13:16 UTC 2016


I'm doing some work on refactoring controller methods, to bring them into line with standard rails naming (i.e. new/create/edit/update/show/index instead of view, list etc).

Part of this involves renaming translation keys, e.g. `diary_entry.view.xxx` becomes `diary_entry.show.xxx`. This means that all the translations are lost, and translators have to re-translation strings that haven't actually changed.

What is the best approach for dealing with this? Can we get translatewiki to handle this situation? Should we add the new translation keys first, to allow translators to copy+paste themselves? Do we just push on and let the translators deal with it? Or something else?

I'd definitely prefer the first - we should be able to fix the translation keys without losing any translations or asking the translators to do make-work. But I don't know what's practical.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1289
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20160915/c57102f1/attachment.html>


More information about the rails-dev mailing list