Hello Kyle!
On Monday, March 26, 2007 at 9:47:04 -0600, Kyle Wheeler wrote:
> Should [$locale] then perhaps be renamed to $date_locale, just for
> more clarity?
Sure yes, good idea! Only if Rado agrees, of course. With a
compatibility synonym. $locale is a very imprecise and confusing name.
> doing a getlocale() every time [...] seems wasteful.
The current code already does 2 setlocale() around each strftime().
Both skipped in English configurations. We would not _add_ any waste.
>>> Add ! everywhere to reget English by default? Humm... OK, today is
>>> only a first step, right?
> NEW! One of the features of mutt 1.6 is more thorough support of
> locales!
Such second step will be much more difficult. Changing default value
of $locale is not enough. For index we'd need various localized default
values for $index_format. Today it contains "%{%b %d}". Month, then
date: English order. The browser has the same problem, not even (yet)
configurable. Attributions need localized default $attribution and
$date_format strings. Surely someone will come proposing some or such
"universal" but impersonal format, nobody will never agree.
But that's the hard way to go. ;-)
I don't even have any idea about how to have various localized
strings as default in a Mutt variable. If gettext comes in, it would
need to follow LC_TIME, not LC_MESSAGES (for people using different
values there). For attributions, a bash script like my "attributer"
could be used, but that's not default values anymore.
Bye! Alain.
--
This mail is confidential. Don't read it. Then after eat your screen.
