Timeline for What was the significance of the cursive 'ƒ' in an application name?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2018 at 15:59 | comment | added | Josh | Point taken, I suppose i should have said that it uses case insensitive ASCII order, that is, essentially all characters were converted to either uppercase or lowercase. I can do some test to confirm, but this is evidenced by another common trick: prefacing a name with a space character (ASCII 0x20) to place it at the top of a list | |
| Feb 23, 2018 at 15:50 | comment | added | Michael Shopsin | @Josh the Finder sort did not use ASCII order, for example a is 0x61 while A is 0x41 but they would get the same priority and a 0x61 would come before B 0x41. Unix style pure ASCII sorts put capital letters before lower case as well as other counter-intuitive sorting with accent characters. | |
| Feb 22, 2018 at 23:06 | comment | added | Josh | @MichaelShopsin that's not a bug -- it's a feature! option-8 produces the bullet character which had a high ASCII code, higher than any letter or number and most other symbols. So it was last in a list of things sorted alphanumerically. | |
| Mar 10, 2017 at 0:08 | vote | accept | Coxy | ||
| Mar 9, 2017 at 16:25 | comment | added | Michael Shopsin | MacOS limited filenames to 31 characters so ƒ was a way to tighten up the name as well. Due to an obscure Finder bug • (option-8) would sort last in the list so users would put that on the front of filenames to make things load last. MacOS and HFS tolerated any characters in MacRoman in filenames except for : the path separator. | |
| Mar 9, 2017 at 3:53 | history | answered | Chris Hanson | CC BY-SA 3.0 |