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

Re: svn:charset

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: Tue, 24 Jun 2008 10:53:55 -0500

On Tue, Jun 24, 2008 at 9:27 AM, Branko ibej <brane_at_xbc.nu> wrote:
> Dag-Erling Smrgrav wrote:
>> The svn:charset property is widely used, and has been for years. There
>> are even clients (e.g. SmartSVN) that rely on it when diffing files or
>> revisions with different encodings.
>> Is there a good reason why it should not be officially sanctioned and
>> documented?
> Do all the clients that use it expect it to conform to the same specs? My
> guess is -- no.
> Whoever intruded on the reserved svn: property name namespace should git off
> their behind and do the groundwork to make sure all uses are consistent,
> then post patches to this list.

Agreed. I've never heard of this property, ever, in the entire
history of the Subversion project. I know that some svn clients out
there have started making use of 'bugtraq:*' properties for
issue-tracker integration, and that's fine. But if clients have
started inventing new svn:* properties, that's a violation of the svn
API -- only 'core' svn libraries are supposed to implement those

Is SmartSVN the only client using svn:charset? Do they document it
somewhere? (Keep in mind that SmartSVN isn't using the svn libraries
at all -- it's a complete third-party implementation of svn in java.
But still, inventing new svn: properties is quite audacious.)
Received on 2008-06-24 17:54:11 CEST

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.