Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index



Everyone has their own way of doing things.

Date formatting is just one of the things.

In the USA we use Month-Day-Year. There was a movement to go metric to be more like Europe, but that failed.

Some place go year-month-day, since the day changes faster than the month and the year. That would make year sorting easier if you do not have a system that would sort dates as a non-number.

So having

Month-Day-Year
Day-Month-Year
Year-Month-Day

as the possible formats can mess people up when you just use 2 digit numbers.

As I said, each country, or professional group, will use whatever date format they prefer to use, was taught to use, or were ordered to use [military].

I do not think we can get everyone to do it the say way. Be nice, but not going to happen.

That is why there are so many different date formats to choose from with most packages that have an ability to format the dates.



On 07/25/2012 03:43 PM, anne-ology wrote:
        Well, the same thing that's wrong with changing the clocks ... ...
.... etc. etc. etc. ... ... ...



On Wed, Jul 25, 2012 at 1:49 PM, Johnny Rosenberg <gurus.knugum@gmail.com>wrote:

2012/7/25 anne-ology <laginnis@gmail.com>:
        yes, I agreed with you -
            except don't blame the U.S. for that silly ISO  ;-)



On Wed, Jul 25, 2012 at 7:00 AM, Joep L. Blom <jlblom@neuroweave.nl>
wrote:
On 25-07-12 10:40, anne-ology wrote:
         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<
http://www.cs.tut.fi/%7Ejkorpela/iso8601.html>for an
explanation of this idea;
                  [it's 'clear as mud'  ;-) ]

  Thanks for your support!
Joep



  On Mon, Jul 23, 2012 at 4:18 PM, Joep L. Blom <jlblom@neuroweave.nl>
wrote:

On 23-07-12 21:02, Andreas Säger wrote:

  Am 23.07.2012 14:44, Guy Voets wrote:
  Hi folks,
A LibO spreadsheet, made in LibO, Dutch version (no Excel or OOo
past).
      - In LibO 3.5.5, I used to give in dates as 20-7 and they were
shown
as 20 Jul 12.
      - In LibO 3.6.0.2, if I enter 20-7, 20-7 is shown in the cell.

If I enter 20-7-12, the date is inverted into 12 Jul 2020.
So instead of entering 20-7, I now need to enter 12-7-20 to get the
desired notation 20 Jul 12.

Is this a new feature, or a bug?


  This is just another anti-feature that has been added to Calc
against
all reason simply because too many inexperienced users who never
really
used any spreadsheets insisted loudly enough.
I will upgrade my LibreOffice 3.5 to ApacheOpenOffice 3.4.1.


   I resent the US way of ISO 8601. We Dutch and other Europeans use
the
more logical sequence of day-month-year instead of the illogical
year-month-day.(most important first, least important last: very often
the
year can be missed).
Joep


Exactly what is strange with ISO 8601?




--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.