|
|
because of UNIX i am guessing..
rob, et al,
actually, it's more clever than that
Try the following: Make a folder in the Finder, and rename it something like "03/30/2002". Note that the Carbon Finder allows slashes (but not colons). [This is because the Carbon framework expects path separators to be colons]
Then open up the Terminal, and ls the directory your folder is in. Note that to the BSD layer, your folder is named "03:30:2002". Clever, eh? [This is because when you made the folder, the Carbon framework translated the slashes, legal in Carbon, to colons, legal in BSD]
But on an HFS+ disk, the filename will be stored as "03/30/2002". On a UFS disk, it would be "03:30:2002". [This is because the Virtual File System layer decides which way it's allowed to store the filename, depending on the filesystem]
This was described in some depth at a WWDC session, and in a USENIX talk by Wilfredo Sanchez, the former BSD guy at Apple.
None of this, of course, explains Office v.X's pigheadishness on the matter. My only guess is that instead of using Carbon calls, they're doing their own more direct manipulation, which munges things up somehow.
actually, it's more clever than that
Agreed, MS apps hate /
I once named my hard disk the single character "/" (This was in OS9 btw). This effectively added a "/" to the path of every file on the disk. Not a single app had a problem except Windows Media Player (the only MS app I was using other than IE). I can't remember if it didn't launch or couldn't play any files, but either way it was totally crippled. Changing the HD name to something else immediately fixed WMP. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.05 seconds |
|