On 2005-05-09 11:52:20 +0200, Peter N. Lundblad wrote:
> On Mon, 9 May 2005, Vincent Lefevre wrote:
> > Now, for ls, this isn't much a problem: non-ASCII characters are
> > just displayed in an incorrect way. But with Subversion, this is
> > much more a problem since it thinks that the filenames have changed
> > (unless this has been improved recently) if the user uses different
> > locales; this is not just a display problem.
>
> I don't understand how making the encoding configurable solves this
> problem.
I recall the problem:
From a UXterm (i.e. UTF-8 locale):
$ touch testé
$ svn add testé
$ svn commit
Then, from an Xterm, with an ISO-8859-1 locale:
$ svn st
? testé
! testé
This is because the locales have changed. Therefore Subversion assumes
that the filename has changed from "testé" to "testé". If the original
encoding is stored somewhere in the .svn directory (here, UTF-8), then
after changing the locales, Subversion will still be able to know the
encoding that was used (UTF-8), therefore will know that the file in
the working copy is "testé", not "testé".
> Why don't GNOME users use an UTF8 locale?
More and more GNOME users (and others) are switching to UTF-8. However
there's still software that doesn't support UTF-8 (or have bad support
for it), in particular, zsh (because of multi-byte characters). In my
case, I'm still using ISO-8859-1 with zsh. The other problem is that
many users still work with ISO-8859-1 / ISO-8859-15 (almost compatible)
text/plain files, and they don't necessarily know how to handle them in
UTF-8 locales.
--
Vincent Lefèvre <vincent_at_vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / SPACES project at LORIA
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 10 01:04:27 2005