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

Ximon Eighteen wrote:
> fact I think I'm probably very confused. I *thought* for a while that
> Gunter was saying that the encoding of data transmitted between anything
> that talks to the repository server (apache, svnserve, whatever) should
> be UTF-8

Yes, it is. (Filenames are UTF8, that is, subversion never deals with the
encoding of the file's contents. I don't know about informational / error
messages, but I supoose it's the same there.)

> and then the repository server never needs to know about any
> encoding other than UTF-8.

"Needs to know" or "Does not need to know"?

In theory it does not need to know any additional encodings, or at least I
thought it wouldn't.

However, as it turned out to my surprise, it DOES need to know a local
encoding which can represent the characters used by the clients within the
filenames. For some reason svnserve seems to decode the UTF8 to its local
encoding while working with the repository, at least temporarily.

> The responsibility for handling encoding
> conversion then falls on the "client" (thing talking to the repository
> serving process) because the protocol over the wire stipulates UTF-8.

Right, that's the way it is.

> If this were the case the hook feature described above by Paul isn't
> necessary because the message would go over the wire as UTF-8 and the
> "client" would convert it to the "local" encoding.

Yes, if subversion handles informational messages as URL strings, it should
work this way.

Greetings,

  Gunter

-- 
Error: Keyboard not attached. Press F1 to continue.
*** 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