On Mar 27, 2007, at 07:33 UTC, Glenn L. Austin wrote: > It's not "wierd" at all. > > HFS file names have a maximum length of 31 bytes (yes, bytes). > > HFS Extended (HFS+) file names have a maximum length of 255 > decomposed Unicode glyphs. > > If you attempt to access a file that has a name longer than 31 bytes > using HFS calls, you'll get the second (CX default cal > 9_16_0#7B558.icc) name.
Yeah, but he's not; he's accessing the file with REALbasic. RB uses the newer, Unicode- and long-file-name-savvy APIs for getting the file name. It's done so for years. That's why it's very weird for him to be seeing the HFS name. > One challenge is that there is no real "HFS+ absolute path" -- Yes, but again, this doesn't matter if you're using RB; RB constructs an absolute path for you using the full name for each part. (This was added a little over a year ago -- before that, the thinking was to return a path composed of HFS names to be compatible with AppleScript, which back then didn't grok long file names in paths. (I think it does in more recent versions of OS X, but I'm not positive about that.) Best, - Joe -- Joe Strout -- [EMAIL PROTECTED] Verified Express, LLC "Making the Internet a Better Place" http://www.verex.com/ _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
