Re: Subversion and Icon files in Xcode projects
Re: Subversion and Icon files in Xcode projects
- Subject: Re: Subversion and Icon files in Xcode projects
- From: Ulf Dunkel <email@hidden>
- Date: Thu, 17 Aug 2006 10:06:14 +0200
- Organization: invers Software
Hi William.
I really wonder why one should use <cr> or <tab> in a filename as it is
strictly NOT recommended. See the Unix filename spec:
- - - - -
File Specifications
The Parts of a File Specification
UNIX filenames really only have two parts: an optional directory
specification and a filename. Directory specifications are delimited by
the forward slash character: /. Filenames may be any ASCII character up
to 255 characters in length. Filenames may even contain non-printable
characters, but this can cause problems when trying to access or
reference a file and is not recommended. It is also not recommended that
the T-shell metacharacters be used as parts of filenames, since these
characters have special meaning to the shell and will make accessing the
file more difficult. A filename in UNIX may even contain spaces. This
will make the specification of the file to some UNIX commands more
difficult, but you can overcome this by putting the filename in quotes
(enclosing in double quotes, such as: "a file").
- - - - -
William Moss wrote:
If anyone is considering bringing this to the subversion developers,
here's a bit of info I noticed. The subversion issue tracker lists a
few mac-specific bugs, but the icon<cr> issue isn't one of them. Most
likely they just aren't aware of the wide impact on their mac users.
More generally though, Subversion does not encode control characters
in filenames. It appears to be issue number 1954 in their issue
tracker and is now listed as "resolved".
http://subversion.tigris.org/issues/show_bug.cgi?id=1954
Last month, Phil Marek (the owner of the fsvs project) brought the
issue back up for discussion since he wanted to add tab character
encoding to filenames and thought adding more control characters in
general might be a good idea. He made two patches for svn developers
to consider, but the discussion sort of died out.
July discussion threads: http://svn.haxx.se/dev/archive-2006-07/
Phil's first email on topic:
http://svn.haxx.se/dev/archive-2006-07/0494.shtml
While I don't know where the issue stands today, the time may be right
to approach the svn developers and make them aware of the impact this
has on mac developers. (In a courteous manner, of course).
http://subversion.tigris.org
William
On 8/14/06, Sean McBride <email@hidden> wrote:
On 2006-08-11 14:25, David Holt said:
>This sounds quite complicated. I'd hoped that the issue had been
>resolved or that there was a better way. I am using Subversion 1.3.2
>
>Does anyone know if Xcode 2.4 resolves the issue?
It's not an Xcode bug. I use svn but not from Xcode (only from svnX and
terminal) and I've seen the same thing. Basically, svn does not like
<cr> chars in filenames. I'd call that a bug in svn, and encourage you
to file it with the svn people.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Bis bald / See you soon / A bientôt / Tot ziens / Ghis revido
invers Software Vertrieb - Inh. Ulf Dunkel
mailto:email@hidden - http://www.calamus.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden