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

Re: [PATCH] $LastChangedDate$ encoding

From: Jesper Steen Møller <jesper_at_selskabet.org>
Date: 2006-04-23 02:15:05 CEST

Peter Samuelson wrote:
> [Branko Cibej]
>
>> That's really not correct. Keywords should be expanded in the file's
>> internal encoding, not the locale encoding. Since we don't *know* the
>> file's encoding, UTF-8 is marginally better than something random,
>> IMHO.
>>
> [...]
>
> In my opinion, the keyword expansions are specific to the WC, and as
> such, should match the encoding of other things specific to the WC -
> like filenames. It should be safe to assume that the user's editors
> and pagers and other tools will default to the encoding from the user's
> environment - at least, that seems to be safer than assuming that the
> user's tools will all treat files as UTF-8.
>
Another use for the proposal to let Subversion handle file content
encoding, see <http://svn.haxx.se/dev/archive-2006-03/1182.shtml>.
(I'm still willing to work on this, but the reception was mixed.)

-Jesprr

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 23 02:12:28 2006

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.