Re: Encoding of .subversion config files?

Philip Martin <philip@codematters.co.uk> writes:

> Do we have or need a policy for the encoding of the config files in
> .subversion? At present it appears that the global-ignores value
> needs to be in UTF-8 while the diff-cmd value needs to be in the
> native encoding.

I've been investigating the existing behaviour a bit more. The first
thing is that httpd doesn't make a setlocale() call so on my Linux box
that restricts Subversion to native/UTF-8 conversions that are trivial
(ASCII only). This doesn't matter for things like paths within the
Subversion filesystem since they never get converted to native, but a
few corner cases like repository paths passed to hook scripts are
affected -- such paths can only be ASCII. The svnserve server does do
make a setlocale call so it can do native/UTF-8 conversions, i.e. it
can pass non-ASCII repository names to hook scripts.

The following is derived from the observed behaviour rather than any
examination of the code:

.subversion/config:
  global-ignores UTF-8
  diff-cmd native
  diff3-cmd native
  editor-cmd native
  auto-props
    pattern UTF-8
    value binary?
  tunnels
    name ? only ASCII seems to work
    value binary? can be non-ASCII

svnserve.conf
  password-db UTF-8 converted to native for open
  authz-db UTF-8 converted to native for open

password-db
  username/password UTF-8

authz-db
  paths UTF-8

httpd.conf
  AuthzSVNAccessFile UTF-8 but only ASCII subset since cannot convert
  AuthUserFile binary? can be non-ASCII

AuthzSVNAccessFile
  paths UTF-8

AuthUserFile
  username UTF-8? client sends UTF-8
  hash binary?

hook scripts
  parameters native
  stderr output native

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org