Yea, I'm with you. Not all of us use UNIXes that rely on such things
so just a smart fallback would be great since UTF-8 support is there,
it's free and most importantly it's an encoding that a project should
be using especially if many committers are on it from different
locations like most open source projects are.
All I really want is a more verbose error that tells the user why svn
can't recode the string or even what that means since the wording is
very ambiguous.
"svn was unable to convert to local encoding. This can be fixed by
setting your LANG or LC_TYPE environment variable." would be a much
better error in my opinion.
-Karl
On 4/28/05, Morten Brix Pedersen <morten@wtf.dk> wrote:
> Hi,
>
> * The Karl Adam <karl.adam@gmail.com> [2005-04-25 19:19:33]:
> > I've run into this error a couple times and have basically resolved it
> > by asking in #svn every time, but the root of the problem is that in
> > order for svn's unicode support to work correctly I need to have a
> > LANG set in my environment vars. The only problem is that on Mac OS X,
> > by default everything is unicode and the LANG property is not set, so
> > we end up with this error whenever weird chars are encountered.
>
> Indeed. I'm sad that no-one has replied to your post on the mailing
> list. This is a very irritating bug. It should have higher priority,
> since it relates to all Mac OS X users which have non-ASCII
> filenames in their repository.
>
> > The problem I'd like addressed is two-fold. One that error is very
> > ambiguous and doesn't actually tell the user what is wrong, how to fix
> > it, or even where to even approach the problem from.
>
> Exactly. The error message should be changed.
>
> - Morten.
>
> --
> http://mbrix.dk/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 2 16:19:46 2005