Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: FSRef under Windows / loading files with special characters in their filenames



You could try making a hard link to the file with the special characters in
its name.  But name the link something very simple like temp0001.  Then,
open the link.  I've gotten around similar problems in the QT player with
this technique.  It seems that the QT player (at least) squawks when you use
some of the more esoteric features of Windows file names such as special
characters, parentheses, and brackets.  Then, when you're done doing
whatever you're doing, just delete the hard link.  

Tom Hesley
Tommy's Tunes


-----Original Message-----
From: quicktime-api-bounces+pulse=email@hidden
[mailto:quicktime-api-bounces+pulse=email@hidden]
On Behalf Of Alexis Glass
Sent: Thursday, September 21, 2006 9:31 AM
To: email@hidden
Subject: FSRef under Windows / loading files with special characters in
their filenames

Looking through the list archives, I found a post from Harry Plate, 
dated Dec 9 2005, dealing with much the same problem as I have -- namely 
that FsRef functions aren't in the Quicktime SDK libraries for Windows, 
though it they are listed in the header files. 

I am trying to load an audio file which uses an 'e' with an acute accent 
in the filename; this fails when I use FSMakeFSSpec or 
NativePathNameToFSSpec. It would seem that under OS X, using FSMakeFSRef 
would would be the appropriate course of action. Given that the function 
isn't available under windows, how do I go about opening files with 
special characters in their names?  Has anyone (Harry?) made any 
progress with this who is willing to share their discoveries?

Thanks very much in advance for any help.

Alexis

(original post by Harry Plate below)

> Ok. So FSRefs really arent supported on windows; I'm surprised... I've
gone
> thru every QT book I have (and the CDs associated) with them, and note the
> FSRef is always qualified w/ some kind of OSX directive.
>
> I note that on windows that an FSRef is declared to be an opaque array
600b
> in length; So what if I write my own implementations for the 3 functions
> below, and like the FSSpec windows implementation, merely copy the
absolute
> filepath into that array? Is this what folks end up doing. Or is there a
> better approach?
>
> Can anyone throw me a bone?
>
> -harry


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/pulse%40prosaic-express
ions.com

This email sent to email@hidden

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden

This email sent to email@hidden

References: 
 >FSRef under Windows / loading files with special characters in their filenames (From: Alexis Glass <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.