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: Paul Berkowitz <email@hidden>
- Date: Wed, 12 Dec 2001 20:21:23 -0800
On 12/12/01 7:58 PM, "Michelle Steiner" <email@hidden> wrote:
>
> I mentioned yesterday that 'alias as string' was returning international
>
> text, not plain strings.
>
>
But this is string as alias, not alias as string. Also, why would it
>
happen only with the volume name, and not with any intermediary folders
>
or the file itself?
But the alias is referenced by the string path, and in international text
the string path is different if the case is different. Or so I thought. But
you're right that it only errors if you change the case of a character in
the disk part of a path. What happens if you change the case of a character
in any other part is that it is coerced to the correct case when you compile
it with 'alias' in front of it. that's not exactly being case-insensitive
(for example, if you compile just the string path without the 'alias' it
stays as the case you altered it to), but rather that a coercion is being
effected. (Also the type face jumps to Geneva 12 as part of the light show.)
I imagine that this may be intentional, not a bug: disks are sacrosanct, and
you could probably have two mounted disks with the same name using different
cases (would the computer refuse to mount the second one? No, I think it
would accept it) whereas you can't give two files in the same folder the
same name, using either case, so a coercion is possible since the existing
file must be the one meant.
Or something like that.
--
Paul Berkowitz