Prefer "block height" instead of "number of blocks".
This was done while testing https://github.com/bitcoin/bitcoin/pull/16981.
Prefer "block height" instead of "number of blocks".
This was done while testing https://github.com/bitcoin/bitcoin/pull/16981.
289 | @@ -290,7 +290,7 @@ 290 | <item row="11" column="0"> 291 | <widget class="QLabel" name="label_3"> 292 | <property name="text"> 293 | - <string>Current number of blocks</string> 294 | + <string>Current block height</string>
Funny that "height" is not in the translations.
ACK b6dcc6d74186eee15eda2cb6e8a7ab5b5b4a05f8. I don't think there are any other obvious examples in the GUI where "block height" should replace "number of blocks" except for translations.
$ git grep --ignore-case 'block height' | wc
65 793 7793
$ git grep --ignore-case 'number of blocks' | wc
141 1125 12941
$ git grep --ignore-case 'block height' -- :^doc/release-notes :^src/qt/locale | wc -l
60
$ git grep --ignore-case 'number of blocks' -- :^doc/release-notes :^src/qt/locale | wc -l
37
Fair enough. I wanted to show that both wordings are used, so it seems arbitrary to change only one?
cr ACK b6dcc6d74186eee15eda2cb6e8a7ab5b5b4a05f8
probably doesn't matter much, but shouldn't hurt either
Fair enough. I wanted to show that both wordings are used, so it seems arbitrary to change only one?
In the GUI this is one, I guess.
block height is probably better because it implies linearity (chain) instead of number of blocks, which could also mean the number of blocks in the block tree.
block height is probably better because it implies linearity (chain) instead of number of blocks, which could also mean the number of blocks in the block tree.
Exactly.