Koen,
RC3 has support for this:
<date_formatter>
<parameter name="format">
<parameter name="nl_BE">d-MMM-yy</parameter>
<parameter name="nl">d MMM yyyy</parameter>
<parameter name="en">M/d/yy</parameter>
</parameter>
</date_formatter>
It falls back to the default for locales where you didn't supply a
format.
This does, of course, also work for <number_formatter> and
<currency_formatter> (very handy in that case because the en_US
locale information we ship has the accounting style pattern for
negative money amounts, with braces, not with a leading minus).
Cheers,
David
P.S: the above patterns are just examples - they're exactly the same
as those for "medium" or "short" in the respective locale definition ;)
Am 12.02.2007 um 15:41 schrieb Dominik del Bondio:
> Hi Koen,
>
> In the latest svn version i added support for supplying extra domains
> when using the formatters. So when using my previous configuration
> example and $tm->_d($time, 'default.my_extra.stuff'); the translation
> domain used to translate the format would be
> dates.my_dates.my_extra.stuff (so, i would change the
> translation_domain
> to "dates" and use _d($time, 'default.my_dates'); and add any more
> formats to the simple translator
>
> regards,
> Dominik
>
> Van Daele, Koen wrote:
>> Hi Dominik,
>>
>>
>> While I'm at it. Here's another question. For some parts of the
>> app I'd
>> like to use one format, for others another. Do I have to define
>> domains
>> for both of them and then decide in the template in which domain the
>> date should be translated?
>>
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.agavi.org/mailman/listinfo/users
>
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
