When I say "alphabetical order", I mean "alphabetical order"

"Last month I have been on a multi-day hike with my dad. Each of us took many pictures, and when we came back we put them all in a shared folder. We both have Android phones, and the naming scheme used for our pictures was the same: IMG_YYYYMMDD_HHmmss followed maybe by some other numbers and then a.jpg. Here YYYY stands for the year, MM for month and so on, so that sorting the pictures in alphabetical order is the same as sorting them by date."

"Or so I thought. Strangely, when I looked at the files from my dad's Windows PC, they were not sorted correctly: all the pictures took with my phone came first, followed by all the pictures took by him. I thought this was surely some weird Microsoft bug - after using Windows 11 at work for a while, I would not be surprised if you told me their file explorer can't figure out how to sort strings."

"But then I looked at the same files in a shared Google Drive folder, and again they were in the wrong order: As you can see, the picture taken at 5:54 (with my dad's phone) comes before the one taken at 9:20 (also with my dad's phone), but after the one taken at 12:11 (with my phone). Weird. Well, maybe Microsoft and Google got this wrong. But that seems unlikely."

Two people returned from a multi-day hike and consolidated photos from their Android phones into a shared folder. Both phones used the same naming scheme IMG_YYYYMMDD_HHmmss (optionally with extra digits) so alphabetical order should match chronological order. Multiple file managers—Windows Explorer, Google Drive, KDE Dolphin, Gnome and phone file managers—displayed an incorrect order, grouping images by phone instead of strictly by filename timestamp. The observer suspected different characters (for example an alternate underscore) but noted that ls on the command line produced the expected, correctly ordered listing.

Read at Tronto