Re: How does subversion handle encodings?

On Thu, 2004-06-24 at 09:23, Marcus Sundman wrote:

> So, how does subversion tackle these issues?

Subversion, by default, will never touch file contents, period. No EOL
conversions, no keyword expansions, no nothing. By default, Subversion
treats all file contents as opaque collections of bytes.

* If you want EOL translation or keyword expansion to happen on certain
files, you must activate these features using the svn:eol-style and
svn:keywords properties, documented in chapter 7.

* The Subversion repository demands that all paths and commit messages
be stored in UTF8. This means that when committing, the client will
attempt to convert local paths (and commit messages) to UTF8, and when
doing a checkout/update, it will attempt to convert UTF8 paths back into
native locale. So if a user commits a Chinese filename, that's fine,
but then you better make sure every other user has a locale capable of
representing that filename.

* Subversion does absolutely nothing in terms of trying to understand
the encoding of a file's text (ascii vs. ucs2 vs. utf8, etc.) Bytes are
bytes. At most, it will change line-endings if you ask.

Does that answer your questions?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 24 16:38:17 2004