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

about character set / encoding conversion in subversion

From: Gunter Ohrner <G.Ohrner_at_post.rwth-aachen.de>
Date: 2006-01-05 12:26:35 CET

Hi!

I want to get more familiar with character set management in subversion to
better understand some issues I'm experiencing. Maybe someone here can
enlighten me or point me to some clarifying documentation.

So far I've always believed, and the docs I found seemed to support it in my
eyes, that subversion converts all file names from a client's custom locale
to UTF8 and only managed UTF8 encoded names internally. I imagined this
conversion to UTF8 would happen in the client before supplying the data to
the server and the conversion back to the clients locale would also be
carried out by the client after receiving the canonical UTF8 encoded names
from the server. That made sense to me as this way the server would not
have to know the (possibly very different) locales / encodings used by the
clients accessing it.

Well, as it seems I was wrong, and the server seems to do parts of (all of?)
the recoding. Now I'm puzzled - how and especially where does the "local
endocing <-> UTF8 conversion" happen inside subversion? Is there any
documentation detailing this and the design decisions behind?

What character recoding is done within the server (svnserve 1.1.4) and how
do I have to configure the server to know all neccessary encodings?

Greetings,

  Gunter

-- 
Tourist, Rincewind decided, meant "idiot".        -- (Terry Pratchett, 
The Colour of Magic)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 5 13:03:46 2006

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

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