[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: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-04-23 13:20:40 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.
>
>
> Let's take that further, then, and say that keywords should be expanded
> in the file's internal _language_, which we also don't know. Should we
> always expand them as POSIX (English), then?
>
> Using the user's locale for the date _format_, but not for the date
> _encoding_, makes little sense to me.
>
> 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.

That makes sense. +1 on using the same locale for both the format and the
encoding of the keywords. (I just saw Ivan's "+1 to English" - with UTF-8 -
which I don't think I agree with, but it's a possibility and is better than
mixed locales.)

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 23 13:21:09 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.