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

Re: Encoding of .subversion config files?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2006-03-03 21:29:34 CET

Peter Lundblad wrote:
> C. Michael Pilato writes:
> > Philip Martin wrote:
> > > 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.
> >
> > Perhaps we should go UTF-8 throughout -- as /etc/subversion/config
> > applies to multiple users who might use different native encodings, I
> > think UTF-8 has a better chance of being transcoded to all of those
> > other encodings. Are there other compelling reasons for going with
> > UTF-8 vs. native vs. free-form (with documentation on a per-option basis
> > as to its expected encoding)?
> >
>
> I'm on the oposite opinion, that we should expect it to be in the
> native encoding. In general, we are UTF-8 internally and natie
> encoding externally and I think that's what we should be. People
> editing their .subversion files will do so in their native
> encoding. The best would be if the encoding could be specified at the
> beginning of the file, but I don't know if that's feasable.

Not to complicate things to an already funky issue, but:
What encoding is used for the mod_authz_svn configuration file? What
about for the svnserve configuration file? What does the DB_CONFIG file
use?

-- 
C. Michael Pilato <cmpilato@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on Fri Mar 3 21:32:55 2006

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