planas,
I don't envy you!
Joep
The ISO is not U.S.;
the U.S. uses the confusing month-day-year rather than the
European day-month-year;
as an historian-genealogist, I've been pushing the European
method.
This ISO is as strange as changing the time twice/year or using AM
or PM following 12: ...
see http://www.cs.tut.fi/~jkorpela/iso8601.html for an
explanation of this idea;
[it's 'clear as mud' ]
These cultural differences can not be resolved by software. This office suite
used to handle these things gracefully.
After all those years since Excel '95 I got used to the input method "23/"
which enters this month's 23th day from any num-pad on any keyboard, in any
office component, under US locale or any other locale.
23/2 entered this year's 23th of February under a non-US locale. US takes
2/23 as February the 23th.
This minimum effort date entry has been given up for some idiots who still
can not tell a string from a number.
Under a German locale I have to leave the num-pad for the point in order to
enter "23.7." instead of "23/".
Date input into Writer tables seems to be completely out of control. I apply
some date format to the entire column, enter a full ISO date and end up with
a text cell.
Bye, bye LibreOffice.
The ISO is not U.S.;
the U.S. uses the confusing month-day-year rather than the
European day-month-year;
as an historian-genealogist, I've been pushing the European
method.This ISO is as strange as changing the time twice/year or using AM
or PM following 12: ...
see http://www.cs.tut.fi/~jkorpela/iso8601.html for an
explanation of this idea;
[it's 'clear as mud']
Thanks for your support!
Joep
yes, I agreed with you -
except don't blame the U.S. for that silly ISO
Exactly what is strange with ISO 8601?
Jonny,
As I said before it's illogic. In my view in a date the least significant (fastest changing) part is the day so it's logical to put it in front.
In the over 2000 years date notation systems are used all logical and illogical combinations have been used.
The reason I find that the current European (Dutch, Swedish) notation is more logical than the ISO 8601 is that in many cases the year notation is omitted which is in the European notation self-explaining but in the ISO 8601 less intuitive.
However, it's my personal feeling and don't forget: international rules aren't always right!
Joep
AFAIK, ISO 8601 is the Swedish notation.
And in order of textual sorting, it is the far most logic notification. But
I agree that mdy is far less logic than dmy or ymd.
Met vriendelijke groeten, Cordialement, Regards,
*DRIES FEYS*
*CORPORATE SERVICES* • *Senior Software Engineer*
As far as I understand the "International" Standard for _ALL_ forms of measurement is -
Left to right, Highest to lowest.
So this makes a Date/Time (which is a form of measurement) Year - Month - Day - Hour - Min - Sec.
All other "measurements" do it this way... $ - c; lb - oz; gal - pint; etc and all Metric Systems as well
G - M - K - (Basic unit) - m - etc etc.
(For clarity and ease of reading I always use the 3-Letter month abbreviation.
So today is 2012 Jul 26!!
Ian W
Pretoria, South Africa.
But that isn't how numbering works! Ten is represented as 10, not 01;
one hundred is 100, not 001.
Moreover, placing ISO-formatted dates in alphanumeric order will
produce chronological order.
It is *very* logical.
If you think it's logical to have the least significant part first, shouldn't that be not "2000 years" but "0002 years"?
;^)
Brian Barker
Hmmm... Year/Month/Day
Drop the year for a moment and you have Month/Day: 7/26
Sounds almost... American style.
I'm in the US, but I save many files which I want to have in chronological order. I always use FileNameYearMonthDate, or Backup20120709.xxx . It is important that if the month or the date is a single digit, it be preceded with a 0 as shown above.
Don
Hi
WoooHooo, at last. I thought i was mad thinking like that but at last someone else has actually said it.
Also was wondering about "millenium" meaning thousand but i can't think of the appropriate word that 'should' have been used instead.
Regards from
Tom