[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: i18n problem

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-08-27 19:31:06 CEST

"Han The Man" <hantheman12@hotmail.com> writes:

> >So the problem here, it seems, is either
> >
> > 1) the initial conversion to UTF8 didn't work, because your FOO
> > locale can't handle international Latin-1 characters. (That's
> > why we have the --encoding option.)
> >
> > or
> >
> > 2) The UTF8 conversion worked, but your FOO locale can't display the
> > international latin-1 characters properly.
>
> The same thing happens when I use TortoiseSVN... no encoding stuff there.
>
> Shouldn't SVN detect this locale stuff?

What are you talking about? It *does* detect your locale. It assumes
your log message is written in your system locale... not a
particularly crazy assumption. :-) It uses this system locale to
convert the log message to UTF8, and uses it again when trying to
display the UTF8 back on your screen. What more 'detection' can it
do? You want it to try and guess the encoding of your log message, by
examining each byte?

> Anyway, what values can "--encoding" take? Couldn't find it in the svnbook.

It takes a locale argument, like "ISO-8859-1". If you're on a linux
box, trying running "locale" to see your system locale, or "locale -m"
to see all available locales.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 27 19:36:14 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.