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

SToring char encoding of files (was: Re: [PATCH] Issue 2332, "$Date$" Keywords always expand with their UTF-8 content)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-12-07 14:07:13 CET

On Wed, 7 Dec 2005, Max Bowsher wrote:

> Hash: SHA1
> Peter N. Lundblad wrote:
> > We really need to allow users to store the encoding of a file via some
> > property, but that's a bigger issue that I would like to come back to some
> > time.
> We already have some use of the charset addendum to svn:mime-type:
> $ svn pg svn:mime-type COMMITTERS
> text/plain; charset=UTF-8
Yes, this is a good candidate. I haven't posted about this because
Ihaven't checked if the charset parameter is valid for all mime types that
we want to support translation/diffing/merging. This is not only text/*.
If this is not the case, we could have svn:encoding, fall back on charset
of svn:mime-type and then fall back on the user's locale. But this is
mostly hand-waving; I haven't checked.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 7 14:08:34 2005

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

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