During the ice ages leading to the WindowsXP OperatingSystem, Neanderthal Windows OS employed a SORTing algorithm that was
BINARY in nature.
Fast-forward to WindowsXP: It employs a new
Character-based file sorting algorithm, which preserves the logical order of FileNames.
How is that for a factoid???
Why do I tell you this?
Well, the problem used to become evident when you attempted to SORT FileNames containing numbers.
My standard FileNaming Convention {data that I generate/save} is to always start FileName with a leading 5-digit date code (mmddyy format, unfortunately).
The following is an example of the problem using 3 imaginary files using my FileNaming Convention:
*In older Windows OS, inside WinExplorer (aka FileManager) >> the FileName order sorted/displayed would have been:
010106_readme.txt
100105_readme.txt
020105_readme.txt
*WindowsXP OS, inside the WinExplorer >> the FileName order sorted/displayed would be:
010106_readme.txt
020105_readme.txt
100105_readme.txt
There are some deep settings inside the WinXP registry that allows you to go back to the old method (a user-based setting). But I can't imagine why anyone would want to do that...
I donot know how Linux handles this
BINARY versus Character-based dilemma, but I would guess it to be a
BINARY sort... ?