We were talking about that in our private messages.
Thank you for pointing this out
Maybe sorting should use LC_ALL=C or LC_ALL=C.UTF-8 before sorting command so it could be always one type of sorting for all systems (it should work like that)
I'll wait if someone responds with a good reason to keep things the way they are. If not, I think I'll go for
LC_ALL=C.
Because systems/servers/OSes differ, we always should give the sorting way for each sorting command (LC_ALL...)
I agree. I just didn't know about the difference, and (before my dedicated server disappeared) never stumbled upon this problem.
If we change that now, we can break peoples' scripts, but we should make one way of sorting forever, that's a engineering idea as it should be
Let's say give it 2 weeks. But I guess most people don't read here, until after I broke their script by changing things
We can see in sorted file, on first page that fits the screen that the sorting differs depending on system or given LC_ALL; it is visible by naked eye that the addresses are sorted other way (mainly lowercase-uppercase are in other order)
Here's the difference:
11111111111111111111HV1eYjP
11111111111111111111HeBAGj
11111111111111111111QekFQw
11111111111111111111UpYBrS
11111111111111111111g4hiWR
11111111111111111111jGyPM8
11111111111111111111o9FmEC
11111111111111111111ufYVpS
vs:
11111111111111111111g4hiWR
11111111111111111111HeBAGj
11111111111111111111HV1eYjP
11111111111111111111jGyPM8
11111111111111111111o9FmEC
11111111111111111111QekFQw
11111111111111111111ufYVpS
11111111111111111111UpYBrS
That is annoying to deal with!
This can of course easily be avoided by sorting the data on your local system before using it. For this project, it's quite easy. But for
all Bitcoin addresses ever used, it can take hours to sort the data.