Re: Slashes in filenames (was: Elementary fie naming question)
Re: Slashes in filenames (was: Elementary fie naming question)
- Subject: Re: Slashes in filenames (was: Elementary fie naming question)
- From: Graff <email@hidden>
- Date: Wed, 14 Jan 2004 12:58:39 -0500
On Jan 14, 2004, at 11:12 AM, Axel Luttgens wrote:
Graff wrote:
On Jan 13, 2004, at 7:27 AM, Axel Luttgens wrote:
The whole matter started with a post from Bernard Azancot, who
encountered problems while trying to save files with names
containing slashes from a 'tell app "Tex-Edit Plus"' script
(December 16th).
Marc and Ken suggested to change the slashes into dashes.
I felt somewhat uncomfortable with that workaround, as something
deeper seemed to be at work.
I first reacted to a statement from Ken, but that provoked a thread
through which I was not sure to recognize my own sentences and
arguments anymore, so that I decided to start a new one ;-)
The fact is that there seems to be a globally inconsistent behavior
with regards to slashes in file names.[1]
Which is really what I was getting at.
Not really the truth.
Initially, on December 17th, you wrote:
The problem is the underlying Unix-like nature of Mac OS X.
You can't have a file name that has a slash (/) in it because
that character is used for separating directories. In the
Finder all slashes (/) are automatically translated to
dashes (-).
At best, this may be viewed as very misleading.
So, before going on the general problem (hence the present thread), I
choosed to first ask whether you really meant the above.
In your reply, instead of re-think about what you wrote, YOU decided
to immediately go off-topic and to start with "It is generally a bad
idea to use certain characters in names".
Don't quote out of context, I was responding to someone who was having
trouble with a file name that had a slash in it. That explanation was
NOT off-topic, it was related to the problem. I was attempting to keep
the answer simple and not get into all of the aspects of the Mac OS X
file libraries converting between slashes and colons automatically and
so on. I did make a mistake in saying that slashes were converted to
colons because to my memory they used to in an earlier version of Mac
OS X.
Here is the rest of what I said:
"Tex Edit+ just hands back an error to AppleScript instead of renaming
the file for you. So all you need to do is to replace the slashes with
dashes in your name-generating code."
Could I have written an essay on exactly how the naming mechanism
works? Sure, that's easy, but really all that was needed was a short
explanation and a solution. Maybe my explanation was not phrased
perfectly but it got the point across: be careful how you name your
files, there could be incompatibilities when they contain slashes.
- Ken
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.