On Mon, 2002-01-28 at 08:29, Jon Trowbridge wrote:
> On Mon, 2002-01-28 at 05:38, Eric M. Hopper wrote:
> > On Sun, 2002-01-27 at 21:37, Jon Trowbridge wrote:
> > > Fine-grained mime types for source code certainly exist. You could mark
> > > the file as text/x-lisp (or text/x-c, text/x-h, text/x-java, etc.)
> >
> > Yes, but then you get into encoding issues. Is your Java in UTF-8 or
> > Unicode? How would you prefer to have it checked out? How about your
> > C?
>
> Encodings are a separate issue from MIME types. There should be a
> svn:encoding property that lets the user mark a file as being utf-8 or
> iso8859-1 or koi8-r or whatever.
>
> It probably wouldn't be a bad idea if utf-8 was implicitly assumed in
> the absence of an svn:encoding tag. I certainly hope that subversion
> isn't assuming that all text files are encoded according to the current
> locale.
Actually, IMHO, there should be default client encodings for various
files. Coding system conversion is trivial and not really a version
controllable change.
On my system, I may have fully Unicode capable editors, and want to just
get it in UCS-32 and have done with it. Some people, with less capable
editors, may be willing to deal with garbagey identifier names and check
it out in UTF-8 or something.
Have fun (if at all possible),
--
Eric Hopper
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:00 2006