On Mon, 2002-01-28 at 11:10, Marcus Comstedt wrote:
>
> Jon Trowbridge <trow@ximian.com> wrote:
>
> > It probably wouldn't be a bad idea if utf-8 was implicitly assumed in
> > the absence of an svn:encoding tag.
>
> Yes it would. A very bad idea in fact.
>
> I for one use ISO8859-1 encoding almost exclusively (with ISO2022 as a
> backup), and would absolutely _hate_ for svn to assume utf-8. If a
> charset has to be assumed in some situation, the default _must_ be
> configurable. I can not stress this enough.
The only problem is that this defeats the entire point of having a
default --- if you check files into the repository with the implicit
assumption that they are encoded in iso8859-1, and if I check them out
and implicitly assume that they are in some funky asian encoding, what
have we gained over the present situation?
At least with utf-8, 7-bit ascii stuff always just works. Choosing
utf-8 is more forward-looking than ASCII, and less US/Western
Euro-centric than iso8859-1.
Now it might be reasonable for you to be able to specify a default
encoding that the client would automatically attach to every text file
you created. Anyway, a good client should be setting the svn:mime-type
and svn:encoding properties automatically, so that the user doesn't have
to worry about it.[1]
-JT
[1] ...unless you decide you want to create a text file named
foo.jpg, of course. :)
---------------------------------------------------------------------
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