I think the native API has been discouraging, if not quite deprecating,
FSSpec stuff in favor of more modern stuff.
Would it work if you used a "file:" type URL and wrapped it with a DataRef?
Back in QuickTime 6.3 or so, Apple was making a fairly big deal out of
improving what you could do with DataRefs in the native API. I haven't tried
it, but maybe...?
I don't believe this is possible in QT Java. The function in question
(Movie.convertToFile()) takes a QTFile, which is just a sub-class of
java.io.File. I don't believe URLs or DataRefs can be used. I don't even
see a DataRef type in QTJ, although maybe I could import something from
the carbon/cocoa/corefoundation java libs. Am I missing something?
As for non-ASCII locales, you should have no difficulty assigning
ASCII-unfriendly names to your test files right now, provided you turn on
some non-ASCII input methods in the "International" system prefs. Or just
copy and paste something in Japanese, like "?????????
?????????????????????.mov" ("Kicktam'sFile.mov"... your fonts may vary), into
the filename in the Finder.
As you said, I can test non-ACII charators in a file by cutting and
pasting, which is how I discovered this problem in the first place.
However, it is not so easy to see what would happen to, say, french text
to a user who's system is setup for, say, Japanese. I suppose I could try
that, too, although it will be quite a bit trickier -- at least for me.
Anyway, thanks for the suggestions!
bjorn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-java mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-java/email@hidden
This email sent to email@hidden
