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.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 3 21:23:36 2006