S
Steve
This issue with Windows XP not correctly displaying multiple file names that
contain numbers is really stupid. And the thing that gets me the most is
Microsoft's lame explaination of why....
"Basically, instead of sorting character-by-character in the file name, any
numeric string is handled as a number. Therefore in the Windows XP example
earlier in this article, 401 is a higher number than 6, so Ie401sp2 is
sorted after Ie6. 501 is higher than 401, 4, and 6, so Ie501sp2 is sorted
last. "
This assumption is just plain stupid. How long has Windows been in
existence. 25+ years and now they try to fix something that should have been
fixed at the beginning. While this rule is technically correct, everyone has
been taught to look at a file name digit by digit to determine its sort
order. Now that everyone is used to seeing it one way, lets throw a monkey
wrench into the mix and confuse everyone.
Lets hope service pack 1 fixes the sort order because the registry fix
didn't
contain numbers is really stupid. And the thing that gets me the most is
Microsoft's lame explaination of why....
"Basically, instead of sorting character-by-character in the file name, any
numeric string is handled as a number. Therefore in the Windows XP example
earlier in this article, 401 is a higher number than 6, so Ie401sp2 is
sorted after Ie6. 501 is higher than 401, 4, and 6, so Ie501sp2 is sorted
last. "
This assumption is just plain stupid. How long has Windows been in
existence. 25+ years and now they try to fix something that should have been
fixed at the beginning. While this rule is technically correct, everyone has
been taught to look at a file name digit by digit to determine its sort
order. Now that everyone is used to seeing it one way, lets throw a monkey
wrench into the mix and confuse everyone.
Lets hope service pack 1 fixes the sort order because the registry fix
didn't