|
Replies
:
12
-
Pages
:
1
-
Last Post
:
Jan 2, 2008 12:26 AM
by: derchris
|
|
|
Posts:
4
From:
Germany
Registered:
Sep 29, 2006
|
|
|
|
Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 9:42 AM
|
|
|
Hello,
I use to have 4 Cities in my WorldClock
- Los Angeles
- New York
- Berlin
- Manila (Philippines)
i.e. we have the 31st Dec 2007 - 17:32 in Germany (Berlin) and the iPhone shows:
* Los Angeles - Today - 08:31 Uhr
* New York - Today - 11:31 Uhr
* Berlin und - Today - 17:31 Uhr
* Manila - 07/12/31 - 00:31 Uhr
For Manila it should be Tomorrow or at least 1st January 2008 ...
a year 2008 bug ...?
iMac c2d 20"
Mac OS X (10.5.1)
iPhone 8GB
|
|
Posts:
5
From:
Minnesota
Registered:
Nov 3, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 12:38 PM
in response to: derchris
|
|
|
I noticed the same thing this afternoon in Minnesota. I show New Delhi and Tokyo as 07/12/31. I posted a photo of this strange behavior on my blog at http://manofwy.blogspot.com/
MacBook Pro
Mac OS X (10.5)
iPhone
|
|
Posts:
13
From:
Hawaii
Registered:
Sep 18, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 1:37 PM
in response to: derchris
|
|
|
Same here. My clock doesn't reflect the international dateline for places I'm tracking. I'd like to check back to see if this will be answered. Thank you.
Dell Inspiron 700m
Windows XP Pro
8 GB iPhone, 1 GB Shuffle, iPod Nano, iPod
|
|
Posts:
83
From:
Herndon, VA
Registered:
Nov 3, 2005
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 4:16 PM
in response to: derchris
|
|
|
I can confirm this. I have two world clocks: DC and London. Right now it says in DC it is 7:16 Today, but for London it says 12:16 07/12/31.
PowerBook G4
Mac OS X (10.5)
iPod 60gb, iPhone 4gb
|
|
Posts:
22
From:
Plano, TX, USA
Registered:
Sep 1, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 7:03 PM
in response to: derchris
|
|
|
Me, too. I'm in Dallas (Texas, USA), but World Clock is showing the wrong date for my relatives in Budapest (Hungary).
I saw on another thread (which I can't find now) that the problem goes away once you reach the new year in your own time zone.
Still this is an embarrassing bug, and we have no way of knowing whether it reflects some deeper bug.
Other rumors say that there will be an iPhone firmware update in the next week, so maybe that fixes this. But we might not know until next year.
Happy new year everyone.
PowerMac G5
Mac OS X (10.4.10)
|
|
Posts:
60
From:
New Mexico
Registered:
Dec 31, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 9:09 PM
in response to: jpgoldberg
|
|
|
See what happens when your phone changes year...might need to power cycle the device.
Dell Inspirion
Windows XP Pro
Media Center Edition
|
|
Posts:
3
From:
Patriots Country
Registered:
Dec 31, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 9:19 PM
in response to: derchris
|
|
|
Are these times correct?
0516: UTC - Greenwich Mean Time
0016: Boston
1416: Tokyo, Japan
1616: Sydney, Australia
In looking at some World Time maps, shouldn't Tokyo and Sydney only be an hour apart?
G4
Mac OS X (10.4.11)
1st Mac: SE/30 1/40, 1989
|
|
Posts:
3
Registered:
Feb 19, 2006
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 11:02 PM
in response to: Agent at Clicquot
|
|
|
Sydney is currently on Daylight Savings Time, so it is now one hour ahead. Speaking for all the times ahead of UTC they look fine. Australian Eastern Daylight Time (AEDT, UTC+11) effects New South Wales south not including Queensland which remains on Australian Eastern Standard Time (AEST, UTC+10).
MacBookPro 2.16Ghz
Mac OS X (10.4.11)
|
|
Posts:
2,189
From:
Denver Colorado
Registered:
Jul 16, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Dec 31, 2007 11:07 PM
in response to: derchris
|
|
|
All times and dates are correct now. It is now midnight January 1 here and the only place that still has a wrong date is Los Angeles because it is 11.05 PM there still. It looks like the iPhone gets confused on January 31. Software update can fix this.
MacBook Pro Core 2 Duo 15 SR 2GB
Mac OS X (10.4.10)
|
|
Posts:
52
From:
Anchorage, AK
Registered:
Dec 22, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Jan 1, 2008 12:28 AM
in response to: hexonxonx
|
|
|
Its Still 11:27 in Alaska too:) We have 30 minutes of 2007 left
HP
|
|
Posts:
2,189
From:
Denver Colorado
Registered:
Jul 16, 2007
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Jan 1, 2008 12:33 AM
in response to: iholla
|
|
|
You guys are so yesterday.
(Oh and I meant December 31 not January 31 in my post above)
MacBook Pro Core 2 Duo 15 SR 2GB
Mac OS X (10.4.10)
|
|
Posts:
2
Registered:
Sep 25, 2006
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Jan 1, 2008 4:18 PM
in response to: derchris
|
|
|
I don't think that this is a bug, but simply a formatting issue. UNIX time stamps use the following format: CCYYMMDDhhmm.SS
CC - The first two digits of the year (the century).
YY - The second two digits of the year. If ``YY'' is specified, but ``CC'' is not, a value for ``YY'' between 69 and 99 results in a ``CC'' value of 19. Otherwise, a ``CC'' value of 20 is used.
MM - The month of the year, from 1 to 12.
DD - The day of the month, from 1 to 31.
hh - The hour of the day, from 0 to 23.
mm - The minute of the hour, from 0 to 59.
SS - The second of the minute, from 0 to 61.
(Reference 'man touch' in Terminal)
Therefore, '07/12/31' is actually 2007 Dec 31 and 08/01/01 is 2008 Jan 1. Maybe this field will be localized in a future software update to match the "Region Format" options under Settings. I will be filing a bug report shortly.
Cheers!
Edit: After posting, the forum reformatted the timestamp format -- to prevent this, I have removed the optional braces around CC, YY, and .SS
Message was edited by: synapsestudios
MacBook Pro - 15"
Mac OS X (10.5.1)
iPhone 1.1.2
|
|
Posts:
4
From:
Germany
Registered:
Sep 29, 2006
|
|
|
|
Re: Worldclock went wrong for "tomorrow" items
Posted:
Jan 2, 2008 12:26 AM
in response to: synapsestudios
|
|
|
If this was an formating issus then it should display 08/01/01 on the firtst case (because Manial was in the new year before my other locations).
Let see what happens next year 
iMac c2d 20"
Mac OS X (10.4.7)
|
|
|
