> One challenge is that there is no real "HFS+ absolute path" -- > although the HFS path idea (using colons between path elements) can > be used to create an "HFS+" path, there is no call to convert that > path to a internal format (FSSpec)
One note: Filenames in FSSpec's are limited to 31 characters, so I doubt you'll see any easy way to convert other than the 9_16_0#7B558 way that OSX handles it. I've always assumed that RB doesn't use FSSpecs internally, but if CopyFileTo has problems, maybe it does? - John _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
