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

Re: [RFC/PATCH] commit messages not 8-bit compatible

From: <cmpilato_at_collab.net>
Date: 2002-05-29 21:30:04 CEST

Marcus Comstedt <marcus@mc.pp.se> writes:

> =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@xbc.nu> writes:
> > I must have missed this in your earlier patches. IMHO, only path names
> > should be in (transformed to) UTF-8. Property contents, including log
> > messages, shouldn't be touched.
> Hm. Any particular reason? Apart from breaking the "all strings
> passed to libsvn_* shall be UTF-8"-paradigm, it would mean that two
> persons, one using a Latin-1 charset and one using an UTF-8 charset,
> wouldn't be able to properly read each others log messages even if
> they are restricting themselves to the common subset of characters.

Subversion should *not* be in the business of doing character set
conversions of any sort, in my opinion. All subversion property
values should be binary, and the interpretation of those bits is left
to policy makers. That is, we may say, "The Subversion repository
uses UTF-8 encoding for all human-readable property values"; somebody
else may say that their repository users should make sure that they
use Shift-JIS encodings for their repository.

> Since there are no properties on log messages, how do you propose that
> the actual character encoding for a log message be recorded?

That information, as you may have inferred from my previous paragraph,
is stored "out of band", in a HACKING file or something, and is
regulated by the repos admins.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 1 14:24:01 2002

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