Hontvari Jozsef wrote:
>I guess everybody who regularly use latin-2 or any other non-latin-1 charset
>will vote to #1. I am pretty sure from past experience that if you do not
>declare explicitly that any text in subversion is UTF-8 encoded, then in
>practice subversion (and its clients) will be typically used as an ASCII
>only application. (That also means that this should not be a client option,
>it must be enforced.)
>
>I do not know what is the situation with Unix, but in Windows using a locale
>has been straightforward for years, and I cannot really imagine how a client
>could miss a conversion. (The only additional feature which should be
>useful - theoretically - if I could temporarily override the assumed
>character encoding when supplying input to a client in file. I mean if my
>locale is Latin-2, but I saved the log message in UTF-8 for example, then I
>would be able to say to the client, that hey, this file is in UTF-8 and not
>in Latin-2.)
>
>
But you /can/ do exactly that on Windows. Even worse, you can change the
input locale used by any program on the fly, without touching the system
locale, and there is *no* way for the svn client (that only sees the
system locale, and the contents of a file) to figure out what happened.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 3 00:17:49 2002