Opened 18 years ago
Closed 17 years ago
#791 closed enhancement (fixed)
Localised timezones
Reported by: | johndrinkwater | Owned by: | nielx |
---|---|---|---|
Priority: | low | Milestone: | Trac 0.11 |
Component: | Website/Trac | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I find it pretty weird reading dates and times which aren't localised to my own. Would be a nice user option. Heck, I'm not even sure what timezone is picked, it doesn't declare itself.
Is there a Trac module to cover this?
Change History (13)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Platform: | → All |
---|
wkornewald - i'm all for that (21/06/2006 is my native ;)), but how does that appeal to international users here?
comment:3 by , 18 years ago
There is a ticket for this on the original Trac:
http://projects.edgewall.com/trac/ticket/1690
It looks like dates always use the system's locale setting.
comment:4 by , 18 years ago
Milestone: | → Website R1.5 |
---|
comment:5 by , 18 years ago
Platform: | → All |
---|
It should be possible to get the locale from the browser and use that.
comment:6 by , 18 years ago
The functions in util.datefmt.py can easily be overwritten either to enforce 8601 formatting (YYYY-MM-DD) or even extend to take user preference into account or even browser setting.
comment:8 by , 18 years ago
Okay, then you can either pass format='iso8601' into every call to format_date* or better still make this the default argument.
comment:9 by , 17 years ago
This is going to be addressed in Trac 0.11. It's probably a good idea to wait for this revision.
comment:11 by , 17 years ago
Milestone: | Website R2 → Trac 0.11 |
---|
comment:13 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I would also be happier about a simple YYYY-MM-DD (2006-06-21) date formatting. I hate the mixed MM/DD/YY formatting.