i18n problem

[Han The Man <ha...@hotmail.com>]

I think I've seen some i18n issues in the tracker, but I'm not sure if my 
problem is related to that.

The thing is, I do a svn ci --message "message with international 
characteres, LATIN-1"

Next, when I do an svn log, the international characters are screwed up (two 
not-so-funny characters for each international character)

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: i18n problem

[Ben Collins-Sussman <su...@collab.net>]

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

> I think I've seen some i18n issues in the tracker, but I'm not sure if
> my problem is related to that.
> 
> The thing is, I do a svn ci --message "message with international
> characteres, LATIN-1"
> 
> Next, when I do an svn log, the international characters are screwed
> up (two not-so-funny characters for each international character)

If your normal console locale is FOO, then when you commit your log
message, svn assumes it was written in locale FOO and converts it to
UTF8, and stores it in the repository.  When you later run 'svn log',
svn converts the UTF8 log-message back into locale FOO for display.

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.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org