On 18 jun, 00:04, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Sun, 2007-06-17 at 06:13 -0700, Jonas wrote: > > The current settings already are unambiguous *only for north > > americans*. > > I'm sorry, but this simply isn't true. > > - Current default DATE_FORMAT is "N j, Y" which, right this > minute, produces "Jun. 18, 2007". > > - Current default DATETIME_FORMAT is 'N j, Y, P' which produces > "Jun. 18, 2007, 8:52 a.m.". > > - Current default TIME_FORMAT is "P" which produces 8:52 a.m. > > - YEAR_MONTH_FORMAT and MONTH_DAY_FORMAT similarly use words for > the month and four digit years. > > None of those are ambiguous. You might quibble (as I would) that using > month abbreviations rather than thefull name there is a flaw, but it's > not fatal and there is absolutely zero doubt about what month, date, > year, hour, minute and half of the day is being referenced. No matter > what your particular locale, providing you know the English month > names. The problem is that you think that everybody would have to know the english months names, and to feel comfortable with the USA date format. In USA is used: *Month Day Year*. But in another countries the people could use another formats like *Day Month Year*
> They are all also marked as translatable by Django, so people using > other languages see localised, similarly unambiguous versions of those > strings. I'm agree. But the settings should be set by default to that international format by I just say in the anterior paragraph. > > Django is a project used by an international community (and grown by > > that community) and its configuration should be set to an > > international format by default. > > "International format" can mean a lot of things, not all of them good. > One very strong argument against using an ISO format (which is > well-defined and is what the original ticket was about) is that it isn't > a very human-friendly string. If your friends asks you what the date is, > you don't say "2007-06-18", you say "June 18". The goal of a date format > is to unambiguously describe the date and time in a way that is > understood by the reader. That is the main justification given in the > links you posted earlier, too, if you have a look. However, none of > those links address the human-readable phase particularly clearly. We > meet the unambiguous and clear in all locale requirements with our > current setup. If a website says "today is 2007-06-18 08:52", it is > designed for people who are very familiar with computers and willing to > compensate for some odd constructs like that; it isn't written to be > invisible. It has not been created to be human-friendly else so that it can be understood by anyone. That's the function of an international format. I don't say that location of date and time shouldn't be used, else that by defect would have to be selected the international format. Or perhaps, does Django has the location about date and time for all countries? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
