> Jonas wrote:
>> I remember to you that we are to interacting with computers, not with
>> persons.
James Bennett wrote:
> The problem is that we're not really "interacting with computers".
> We're using computers as proxies to help us interact with *people*,
> and they should be first in our
On 6/19/07, Jonas <[EMAIL PROTECTED]> wrote:
> It's true that we are around circles, and I understand that you wann't
> make that little change. It's more comfortable to have the framework
> configured to your localization that:
And it's already quite easy to do so, just by changing a couple
On 6/19/07, Jonas <[EMAIL PROTECTED]> wrote:
>
> On 18 jun, 23:17, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > I'm going to give this one more pass and then dropout. We're just going
> > around in circles now.
> It's true that we are around circles, and I understand that you wann't
> make
On 18 jun, 23:17, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I'm going to give this one more pass and then dropout. We're just going
> around in circles now.
It's true that we are around circles, and I understand that you wann't
make that little change. It's more comfortable to have the
I'm going to give this one more pass and then dropout. We're just going
around in circles now.
On Mon, 2007-06-18 at 12:09 -0700, Jonas wrote:
> On 18 jun, 00:04, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > On Sun, 2007-06-17 at 06:13 -0700, Jonas wrote:
[...]
> The problem is that you
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"
On Sun, 2007-06-17 at 06:13 -0700, Jonas wrote:
> On 17 jun, 09:03, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> > On Sun, 2007-06-17 at 00:54 -0700, Tai Lee wrote:
> > > +1 - it's a simple default settings change. django is used by an
> > > international community, so the defaults should be a
On 17 jun, 02:01, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> (also the patch should have been against
> global_settings.py, not settings.py, but that's a minor thing).
It's already corrected.
--~--~-~--~~~---~--~~
You received this message because you are
On 17 jun, 09:03, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Sun, 2007-06-17 at 00:54 -0700, Tai Lee wrote:
> > +1 - it's a simple default settings change. django is used by an
> > international community, so the defaults should be a format that is
> > understood by everybody without any
On Sun, 2007-06-17 at 00:54 -0700, Tai Lee wrote:
> +1 - it's a simple default settings change. django is used by an
> international community, so the defaults should be a format that is
> understood by everybody without any possibility of ambiguity. those
> that prefer a different format
+1 - it's a simple default settings change. django is used by an
international community, so the defaults should be a format that is
understood by everybody without any possibility of ambiguity. those
that prefer a different format (american, or abbreviated or full
length month names etc) can
On Sun, 2007-06-17 at 01:58 +, [EMAIL PROTECTED] wrote:
>
>
> On Jun 16, 6:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> > > However all that is beside the point. The patch that Jonas has posted in
> > > #4590 is just
Since this has come up, may I point you to this discussion over here:
http://groups.google.com/group/Django-I18N/browse_thread/thread/3f5dfb2a9a10f904/54365cef61f62f21?lnk=st==1#54365cef61f62f21
About ticket 4147: http://code.djangoproject.com/ticket/4147
On Jun 17, 4:58 am, "[EMAIL
On 6/16/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> However all that is beside the point. The patch that Jonas has posted in
> #4590 is just to change the default settings. I'm not sure if that's
> worth doing or not. Currently I'm somewhere between -0 and +0, since
> it's completely
On Sun, 2007-06-17 at 02:50 +0200, Julian 'Julik' Tarkhanov wrote:
>
> On Jun 17, 2007, at 2:46 AM, Jonas wrote:
>
> >
> >
> > On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
> > > Where do you propose this be used? At the database level, your DB
> > > will
> > > store date/time
On Jun 17, 2007, at 2:46 AM, Jonas wrote:
>
> On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
>> Where do you propose this be used? At the database level, your DB
>> will
>> store date/time values in whatever internal format it prefers.
> Yes, I think that should be stored so at
On 17 jun, 01:14, "James Bennett" <[EMAIL PROTECTED]> wrote:
> Where do you propose this be used? At the database level, your DB will
> store date/time values in whatever internal format it prefers.
Yes, I think that should be stored so at the database level.
> At the
> level of input and output
On 6/16/07, Jonas <[EMAIL PROTECTED]> wrote:
> I think that Django should use an international standard date and time
> format.
Where do you propose this be used? At the database level, your DB will
store date/time values in whatever internal format it prefers. At the
level of inpu
For if you want follow that standard I've added a patch:
http://code.djangoproject.com/ticket/4590
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
I think that Django should use an international standard date and time
format.
For more information:
http://www.cl.cam.ac.uk/~mgk25/iso-time.html
http://www.w3.org/QA/Tips/iso-date
http://en.wikipedia.org/wiki/ISO_8601
--~--~-~--~~~---~--~~
You received
20 matches
Mail list logo
