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

Re: Non Ascii chars in paths cause trouble

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-09-22 12:39:24 CEST

Wednesday, September 22, 2004, 4:46:35 AM, Lübbe Onken wrote:
[snip]
>> You can dump your repositories, find the paths which are not correctly utf-8
>> encoded, replace the invalid characters with valid utf-8 characters and try
>> loading the dumpfiles. That's all I can advise you to do. It's not much, a
>> lot of work, but it's possible.
> Ouch, I was afraid of that answer. So the only thing left to me is
> dumping, grepping "Node-path"s for accented characters and replacing them?
> But what about accented characters inside my source? Should they be
> UTF-8 in the dumpfile as well or are the file contents not touched by svn?

File contents are never touched by svn. So you don't need to worry
about that. Right now it's just the node paths.

[snip]
> That makes me hope that the log messages are at least dumped&loaded OK.

They are. That's one feature that's been working for a long time. :-)

> But:
> - Why does 'svn log' on windows display ?\195?\182 instead of 'ö'?

I recently ran into this problem myself. I had to set APR_ICONV_PATH
to 'x:\path\to\svn\iconv' to get them to display correctly. I believe
TSVN took a different approach to solving this problem (of having to
set APR_ICONV_PATH), which is why you don't this issue with it.

[snip]

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 22 12:39:51 2004

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