aboutsummaryrefslogtreecommitdiff
path: root/src/script/standard.cpp
diff options
context:
space:
mode:
authorMarcoFalke <falke.marco@gmail.com>2018-05-30 09:37:57 -0400
committerMarcoFalke <falke.marco@gmail.com>2018-05-30 09:38:20 -0400
commit25d2df2aa988cfaa086c45854671d56a95a9a7e1 (patch)
tree5e0e1507cf6b03bad86cdc3de7badad8b4f05c97 /src/script/standard.cpp
parent60f0358b4a1ee75bd02773e0eaa5dfd121389f25 (diff)
parent3d4fa83587759095b7f0ccfe4075808098d4ae7f (diff)
downloadbitcoin-25d2df2aa988cfaa086c45854671d56a95a9a7e1.tar.xz
Merge #13341: Stop translating command line options
3d4fa83587 Stop translating command line options (Wladimir J. van der Laan) Pull request description: Many options are extremely technical, and refer internals, making it difficult to translate usefully. This came up in discussion of e.g. #10949. If a message is not understood by translators (which are typically end-users, not developers) they'll either translate it literally, making it harder to understand instead of easier, with the added drawback of the user no longer being able to google it. Also the translation was only working for bitcoin-qt as with the console programs, there is no translation backend. So it was injecting never-used translation messages for bitcoin-cli, -tx. For these reasons, stop translating options help completely. This should not affect the output **in any way** \* except for bitcoin-qt when a non-English language is configured in the locale. This implements #10962. \*) I checked this, but please do verify this. Tree-SHA512: 46c5f2ac0d4dbe9a6710fab498781e442dd6d6ac17613a99fcfe7a62bf6811fa1c92400d35bd389772cb4b31c6918df261548cbc677addba653f44083b9aeeda
Diffstat (limited to 'src/script/standard.cpp')
0 files changed, 0 insertions, 0 deletions