new clock plugin

[Bernhard Walle]

* Brian J. Tarricone [23.10.2005 12:53]:
> 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.

I thought of one default date format and one default time format. If
someone wants something else, he could specify a strftime() string. But
we need a good default. I don't want to explain my grandmother how to
specify strftime() strings but I think she is lucky if she read
"18:18", but I think she don't want to read "6:18 pm".

But, anyway, it just was an idea, I don't have a strong opinion on this.

Regards,
  Bernhard