RE: Difference between "as alias" and "as file specification"?
RE: Difference between "as alias" and "as file specification"?
- Subject: RE: Difference between "as alias" and "as file specification"?
- From: Joe Kelly <email@hidden>
- Date: Wed, 12 Dec 2001 20:29:18 -0800
Paul Berkowitz wrote: "Another result, as I said then, is that the Finder
can't cope with this sort of
string (international text) at all: you have to coerce it to 'as Unicode
text' before the Finder will accept it (although I think it still accepts
plain non-international strings) . "
I've never given much thought to what "international text" was. I always
assumed it was some kind of double byte format or more specifically unicode.
Either way it never figured much in my scripting -- I always coerced it into
a string when passing it to something that couldn't cope with international
text (which seems to be most everything out there). They should just make
string unicode based, and provide implicit coercion for converting it to
single byte strings for legacy apps and osaxen. It would slow things down
for a while, at least until app writers do the conversion. (Oh, and it would
drop any non ascii characters -- all 60000 of them, but hey.)
Paul also wrote: "The real coding for 'file' now is something called
fileURL"
I take it this is synonymous with the OS X url file spec, which is simply a
unicode path string (with url stylings), right?
joe