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

RE: "Can't recode string" again...

From: Gunter Ohrner <G.Ohrner_at_post.rwth-aachen.de>
Date: 2006-01-05 20:02:09 CET

Hunkel, Manfred wrote:
> | However I tried to find information on svn and libiconv and could not

> That's correct. Configure should be able to figure that out
> automagically. (...)
> Did you build your client/server yourself?

Yes and no, I'm using the stock Debian package for subversion 1.1.4 on the
server and a rebuild Debian package for 1.2.3 containing the
meta-data-branch-patch on the client.

> Can you check the output when running configure? -- I'm seeing:
> checking iconv.h usability... yes

It this the output of Subversion's configure, or of Apache's configure?

I ran both configure of svn 1.2.3 and 1.1.4 and none of these shows any line
containing the string "iconv", neither that it succeeded nor that it fails.
Verifying this, grep doesn't find the string "iconv" in configure at all:

$ grep -i iconv configure

> | One thing I *still* do not understand is why the server tries to to any
> Mmhhh... What exactly do you mean by "server" here? The way I understand


> messages. To be able to display these correctly, any client will have to
> convert from UTF-8 to the encoding employed by system the client runs on.

Yes, that's what I though as well, but "strace" shows the error is
originally received via network from the server by the client, which is
what puzzles me... (That is, svn [the client] sends a request, svnserve
gets it and answers "Can't recode string", which is then displayed on the
console by svn [the client].)

> have it. So it's not a matter who exactly does the recoding, but rather
> that generally recoding has to take place for strings on their way
> into/from the repository. Anybody please correct me if my explanation
> provides a false picture of things...

Yes, but just as you did I expected the recoding to take place on the client
side, where it can be controlled using the LC_* / LANG environment

The server answering "Can't recode string" to the client's request looks
suspicious to me, this shouldn't happen at all from how I understood svn's
way to deal with strings...



"Wo ein Killer ist, ist auch einer weg"
        -- Autor unbekannt
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 5 20:42:20 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.