Re: [PATCH] $LastChangedDate$ encoding

[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.