FWIW, we've had a `collate NATURAL_ORDER` in our app for years. Windows Explorer uses *Natural Ordering*, and many users as used to it, and request it of software vendors. We support both case-sensitive and case-insensitive versions, but not your *Dictionary Order*, which is a mix of both. Interesting. I never considered that particular ordering. PS: *naive* implementations convert to integers, and risk overflow, while it's relatively easy to support arbitrarily long integers.