On Nov 29, 2008, at 11:39, Albert Shih wrote:
> I've repository running under subversion 1.4.x under Linux.
>
> They are various clients (OS-X, Linux, FreeBSD). And each client
> have he
> own encoding configuration. Lots of those modern editors convert on
> the fly
> the file. So if a file is in ISO-8859, and someone on a MacOS
> client edit
> this file and commit. It's become UTF-8 etc.
>
> How you manage that ? How can each client have is own encoding
> configuration ?
Subversion does not do anything to prevent this situation. You should
instruct your users to configure their editors to not automatically
convert files.
On Mac OS X, I use TextWrangler, a free editor from Barebones
Software which correctly detects files' encodings and line endings
and lets you edit them as-is (or, if desired, convert them to other
encodings or line ending styles). I'm sure there must be reasonable
editors one can use on Windows, Linux and BSD as well that will leave
the control of encodings and line endings in the hands of the user.
Actually I've never heard of an editor on Mac OS X that would auto-
convert; which one is it, so I can avoid it? :)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-29 20:53:40 CET