diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2020-08-29 10:03:41 +0200 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2020-08-29 10:03:45 +0200 |
| commit | baf9cedee89f34a391b11240984c27b162bccdba (patch) | |
| tree | fce93468450568c4b4da4e01c0184a586121f21d /src/rpc/mining.cpp | |
| parent | 1cf73fb8eba3b89a30d5e943deaec5052a8b21b7 (diff) | |
| parent | ca185cf5a14b16d61814d7172284bc8efcd28b69 (diff) | |
Merge #18817: doc: Document differences in bitcoind and bitcoin-qt locale handling
ca185cf5a14b16d61814d7172284bc8efcd28b69 doc: Document differences in bitcoind and bitcoin-qt locale handling (practicalswift)
Pull request description:
Document differences in `bitcoind` and `bitcoin-qt` locale handling.
Since this seems to be the root cause to the locale dependency issues we've seen over the years I thought it was worth documenting :)
Note that 1.) `QLocale` (used by Qt), 2.) C locale (used by locale-sensitive C standard library functions/POSIX functions and some parts of the C++ standard library such as `std::to_string`) and 3.) C++ locale (used by the C++ input/output library) are three separate things. This comment is about the perhaps surprising interference with the C locale (2) that takes place as part of the Qt initialization.
ACKs for top commit:
hebasto:
re-ACK ca185cf5a14b16d61814d7172284bc8efcd28b69
Tree-SHA512: e51c32f3072c506b0029a001d8b108125e1acb4f2b6a48a6be721ddadda9da0ae77a9b39ff33f9d9eebabe2244c1db09e8502e3e7012d7a5d40d98e96da0dc44
Diffstat (limited to 'src/rpc/mining.cpp')
0 files changed, 0 insertions, 0 deletions