charset property (was: [RFC/PATCH] commit messages not 8-bit compatible)

[Greg Stein <gs...@lyra.org>]

On Thu, May 30, 2002 at 05:44:22PM +0200, Marcus Comstedt wrote:
> 
> Karl Fogel <kf...@newton.ch.collab.net> writes:
> 
> > For example, file contents can be text without being UTF-8!  (And
> > imagine how would people react if Subversion enforced UTF-8 for all
> > text files.)
> 
> Yup.  The thing here though is that for files it's possible (and
> perfectly reasonable) to have a property declaring the used charset.
> Thus the information is not lost.  You could even hack Emacs to
> actually look at the charset property and select the correct MULE mode
> when you open the file.

Yup. This has already come up. Much like we have svn:mime-type to declare
the mime type of a file (and served by Apache via the Content-Type header),
we can also have svn:charset property, which also gets served as part of the
Content-Type header.

For example:

  Content-Type: text/plain; charset=iso-8859-12

or

  Content-Type: text/plain; charset=euc-kr


Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org