Now the United State table is different is not the year 2010 month June the
day 30, then Wednesday.

It is the  of June on the day  30, in the year of 2010.   Now why the United
States does this is beyond me. It is confusing to most who use the ISO
International Standard. I more then likely am wrong but isn't open office a
U.S. Company owned. There is the reason for the stand that Open Office uses.
It is a U.S. A. Standard.

So Open Office why not have both standards let those use the one they want
to use themselves. Have some one write up the little file to let us users
make the choice they want.  I would like to have the 
International Standard ISO 8601 which most countries use including Canada.




Have A Great Day
http://groups.yahoo.com/group/quiltexpression4/
-------Original Message-------
 
From: Bernhard Dippold
Date: 06/30/10 15:45:58
To: [email protected]
Subject: Re: [discuss] [OT (but where else to ask?)]: Timestamp
 
Hi Jonathon, *
 
jonathon schrieb:
> [...]
> And that is yet another answer that ignores John's question.
>
> The questions John is asking are:
> * Why does OOo not adhere to the ISO standard for its default date and
> time notation, but uses a date time system that is, at best,
> confusing;
> * What possible functionality could anybody ever see in the weekday,
> month, day, year formatting that OOo uses as its default;
>
No - John doesn't ask anything about OOo and ISO standards or OOo's
default formatting, he just wanted to know, why in Issue Tracker the
timestamps have a strange format (starting with the weekday, then month,
day, time, time shift from UTC and  year).
 
Best regards
 
Bernhard
 
PS: Sorry that my last mail (and some other in the past) had to be
moderated - for any strange reason SeaMonkey decided to use my OOo alias
for mails to this list - other OOo lists (I subscribed to in the same
way as here) use the right mail address when I post mails.
 
 
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
 

Reply via email to