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

Re: How does subversion handle encodings?

From: Marcus Sundman <sundman_at_iki.fi>
Date: 2004-06-28 12:13:01 CEST

On Thursday 24 June 2004 17:35, Ben Collins-Sussman wrote:
> 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.
> [...]
> * 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?

Mostly, although it was not the answer I was hoping for.
One thing is still not clear: Can subversion have a "type" metadata
associated with each file? (Not storing that crucial piece of info would be
really, really stupid since that would render most text files useless as
text files. That is, unless you send that piece of info in some other way
to everyone using those text files.)

- Marcus Sundman

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 28 12:13:27 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.