Skip to content

Conversation

laanwj
Copy link
Member

@laanwj laanwj commented Dec 1, 2015

But keep translating them in the GUI.
This - necessarily - requires duplication of a few messages. This would allow using different messages in GUI and RPC, but keep them the same for now.
Alternative take on #7134, that keeps the translations from being wiped.

Also document GetWarnings() input argument.

@laanwj laanwj added the GUI label Dec 1, 2015
@laanwj laanwj force-pushed the 2015_12_warnings_translations branch from 99be01c to 1a514e6 Compare December 1, 2015 08:57
But keep translating them in the GUI.
This - necessarily - requires duplication of a few messages.
Alternative take on bitcoin#7134, that keeps the translations from being wiped.

Also document GetWarnings() input argument.

Fixes bitcoin#5895.
@laanwj laanwj force-pushed the 2015_12_warnings_translations branch from 1a514e6 to aabc897 Compare December 1, 2015 09:07
@jonasschnelli
Copy link
Contributor

Nice! This is the right way to do it.
utACK.

@maflcko
Copy link
Member

maflcko commented Dec 1, 2015

utACK aabc897

@laanwj laanwj merged commit aabc897 into bitcoin:master Dec 1, 2015
laanwj added a commit that referenced this pull request Dec 1, 2015
aabc897 rpc: Don't translate warning messages (Wladimir J. van der Laan)
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants