"Migrate Wallet" is unclear to translators
luke-jr opened this issue · 9 comments
Going through translations, I'm seeing things that suggest "migration" is being misinterpreted in the sense of animals migrating (moving/relocating). We could clarify with translator comments (assuming translators actually see them), but that won't help if non-native English speakers are using Bitcoin Core in English, so maybe a better approach is to come up with another word for this?
A better user-facing word would be just "upgrade wallet"--but for technical reasons we use a different word, as we already had a concept of upgrading inside the wallet format.
Some other suggestions, none I'm particularly favourable towards vs "migration" from an English standpoint tbh:
- transition
- convertion
- transformation
Of these IMO only "transition" is likely to have any chance at being more clear (than "migration" apparently is) when translating into other languages.
FWIW "migrate" has a definition as a computer (or information system) term in common dictionaries, e.g.:
https://www.merriam-webster.com/dictionary/migrate
https://www.dictionary.com/browse/migrate
It's also not a Bitcoin-specific invention, but used in many projects (although probably not so often in end user communication). Could it be that those translators simply used some machine translation that was missing the context?
That being said, "upgrade wallet" would definitely be easier to understand.
Migrate is a term that is used in other computer related contexts, e.g. "database migration". It was chosen because of the process's similarities to a database migration, and particularly in a way similar to how Django uses it. Since Django has similar usage of the term with translations, perhaps we can point translators to there?
While "upgrade" was considered, we're already using that to mean something else, and I don't think overloading that term would be helpful.
Can we close this now then? We're not going to find a more appropriate word than "migrate" for this context, and it seems like there's therefore no action to be taken here.
I think context can be added to translations, if it isn't already there. See for example 3868ba3.
Oh ok, great! I wasn't aware that we could add context like that.
An alternative may be to call it "Migrate Wallet Database", not sure which one is better, if any at all. I think if someone cares, they can open a pull request?
Can we close this now then? We're not going to find a more appropriate word than "migrate" for this context, and it seems like there's therefore no action to be taken here.
Agree, i don't think using any another word is a substitute for good explanation in this case, and changing it at this point after having used 'migration' for years would only add to the confusion.