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

Subversion on Solaris, problems with special characters

From: Mathias Weinert <mathias.weinert_at_gfa-net.de>
Date: 2006-02-17 16:48:02 CET

Hi there,

I want to use Subversion on a Solaris system and encouter a
problem with special characters like ä (a with two dots on top).

I am using
svn, version 1.2.3 (r15833)
compiled Nov 7 2005, 06:06:15

I found a post on this list from August 2004 where someone
reports exactly the same but unfortunately I can't get a
solution out of this thread.

So here the description:

I have a repository containig a file täst.txt.
Without setting LANG and LC_... I get:

$ svn ls svn://myrepos/trunk/umlaut
t?\195?\164st.txt

$ svn co svn://myrepos/trunk/umlaut
svn: Safe data 'umlaut/t' was followed by non-ASCII byte 195: unable to convert to/from UTF-8

When I set LC_CTYPE to de_DE.UTF-8 I get:

$ svn ls svn://myrepos/trunk/umlaut
täst.txt

$ svn co svn://myrepos/trunk/umlaut
A umlaut/täst.txt
Checked out revision 228.

$ ls -l umlaut
total 0
-rw-r--r-- 1 weinert weinert 0 Feb 17 16:38 täst.txt

$ touch umlaut/täst2.txt

$ ls -l umlaut/
total 0
-rw-r--r-- 1 weinert weinert 0 Feb 17 16:38 täst.txt
-rw-r--r-- 1 weinert weinert 0 Feb 17 16:39 täst2.txt

$ svn add umlaut/täst2.txt
svn: Valid UTF-8 data
(hex: 75 6d 6c 61 75 74 2f 74)
followed by invalid UTF-8 sequence
(hex: e4 73 74 32)

Setting LANG and/or LC_ALL to de_DE.UTF-8 doesn't change the
behaviour.

Does anybody have an idea what I have to do to be able to
correctly get the file with the umlaut from the repository
and to be able to add new files like this?

Many thanks for any help!

Mathias

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 17 17:01:15 2006

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

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