Ben Collins-Sussman wrote:
> 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.
We're just wildly agreeing here... It would be silly if the server cared
about text/binary (CVS does it this way too although its sucky diffing
algorythm tends hide the fact). The client, though, is responsible for
turning the user file into something the protocol understands... Since
UCS2 == Text then it should be the clients' responsibility to then
encode this in UTF8 for transmisison/storage, and back again on an
update, which is similar to eol-translation (but with more impact on the
filesize)... With that you get keyword expansion and diffing for free.
Like I said, it should be relatively trivial to come up with a patch
that does it... once I can get the damned thing to compile :) Maybe
I'll give up trying to compile it on Win32 and code on Linux for a change...
Received on Wed Jul 16 19:27:07 2003
This is an archived mail posted to the Subversion Dev