Tony Hoyle <tmh@nodomain.org> writes:
> kfogel@collab.net wrote:
>
> > If you're using ra_svn (the svnserve daemon & friends), I'm not sure
> > such a feature is implemented yet.
> >
> Ahh OK. I'd rather hoped that remote users could set ACLs on branches
> to lock them down (code freeze etc.)
>
> >>6. How do you handle UCS-2 files? We have large numbers of these...
> > Like any other file (we don't distinguish between text and binary,
> > though you might want to avoid setting the svn:keywords or svn:eol
> > property on those files!).
>
> So you don't convert to UTF8 and back... hmm.. might not be so useful
> since if you're treating the unicode files as binary they won't merge
> properly :(
Let's clarify some stuff here:
* file names
Subversion treats all file names (and paths) as UTF8 internally.
That means incoming paths get converted from native locale to
UTF8, and paths coming out of the repository get converted from
UTF8 to native locale.
* file contents
The Subversion repository and network layers treats all file data
as bytestrings... there's no notion of 'text' or 'binary' type.
The Subversion *client* (libsvn_wc) looks at metadata attached to
files in the working copy, and distingusishes between text and
binary files. Text files are considered "okay" for contextual
merging (during an update), eol-translation, and
keyword-expansion. Binary files aren't eligible for these things.
Does this make more sense, Tony?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 16 18:20:07 2003