new clock plugin

[Brian J. Tarricone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bernhard Walle wrote:
> * Brian J. Tarricone [23.10.2005 12:14]:
> 
>>Bernhard Walle wrote:
>>
>>>>* Brian J. Tarricone [23.10.2005 09:35]:
>>>>
>>>>
>>>>>We can also debate what the pre-selected date/time formats should be
>>>>>later ^_~.
>>>>
>>>>I think it should be part of the translation so that each translator
>>>>could choose the most "native" date format. E.g. in USA it's common to
>>>>write "Oct 23 2005" (or with some dots and commas, I don't remember ;)),
>>>>in Germany "23.10.2005" is the most common representation, or the whole
>>>>month ("23. Oktober 2005").
>>
>>That sounds like a cool idea, but it's a bit complicated and
>>inconsisten, so... sorry, but no.  If you want to go beyond the
>>defaults, you always have 'man strftime', which is what you had to do
>>with datetime regardless.
> 
> Hm ..., can you explain why this is complicated?

Because you're turning a fixed-length list into an arbitrary-length
translatable list.  Or can you guarantee that you (and all translators)
want exactly 4 locale-specific time formats and exactly 11
locale-specific date formats?  Otherwise it just seems rather messy to me.

There's useful localisation, and there's unnecessary work.  This falls
into the latter category, IMHO.  If someone else wants to implement it
at some point, without doing something ugly, that's fine, but I don't
really want to.

	-brian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDW2vA6XyW6VEeAnsRAvHnAJ9EfK0w6rOa+QPoDs3eo5yUC+x5swCg5QGU
ErQEzb/ekzQZkmIauLsYvq8=
=OymG
-----END PGP SIGNATURE-----