Re: How does subversion handle encodings?
* Marcus Sundman <email@example.com> [2004-06-28 04:12]:
> > 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.)
Yep, check out the svn:mime-type property:
Michael W. Thelen
Experience is what you get when you don't get what you want.
-- Dan Stanford
Received on Mon Jun 28 19:02:43 2004
This is an archived mail posted to the Subversion Users