datestr seems very naughty. http://bazaar.launchpad.net/~anandology/webpy/webpy.dev/annotate/aaronsw%40frabjous.local-20080415164919-woyr1kh87cb7ju5l?file_id=75%402c515a54-6b0d-0410-94c8-a23cf037ada6%3A%3Atrunk%252Fweb%252Futils.py#L468
When Babel does the second part of it (no relative time), using the given locale. http://babel.edgewall.org/browser/trunk/babel/dates.py Then it's about defining what a web framework does and doesn't, and that's up to you I guess. Things that are en_US related appear to me that they shouldn't. web.numify don't like unicode string for instance (which is not a big issue though). Cheers, -- Yoan On Thu, Apr 17, 2008 at 1:44 AM, Yoan Blanc <[EMAIL PROTECTED]> wrote: > ;-) > > And no, I don't know if those functions exists. > > -- Yoan > > > > On Thu, Apr 17, 2008 at 1:43 AM, Aaron Swartz <[EMAIL PROTECTED]> wrote: > > > > web.py has never been great about i18n; we need to fix functions like > > datestr too if we go that route. Considering the current situation > > tho, I don't think including nth_string is unreasonable. > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
