There was a useful little toy in KDE 3 called 'kworldclock', which showed the current times around the World when the mouse moved over them. The appropriate place for this information in KDE 4 is Marble & the datasheets for cities do show their timezones, but not the actual current time there. Would it not be very easy to add a line to the datasheet box giving the current local time ? -- the information is easily available via 'timezone-data' (its name as a Gentoo package, presumably available everywhere) & it should be trivial to add the line to the box. Reproducible: Always Steps to Reproduce: 1. Run Marble. 2. Notice missing information. 3. Actual Results: Current local time not given. Expected Results: Current local time should appear in each city's datasheet.
I am using Marble 4.8.5. I see the time for each city being displayed in terms of offsets of the UTC in the datasheet of the city. Would you like for it to display local time instead of this ? I would like to take up this bug if you feel that it needs to be changed.
I didn't installed Marble on my current Gentoo Linux system, but have just added it. The city information does now include the offset from UT, but is 1 hour fast everywhere, incl London, which should be UTC+0.0 , but shows UTC+1.0 ; my system clock shows the correct offset from UT. So this looks like a new bug.
Hello, (In reply to comment #2) > I didn't installed Marble on my current Gentoo Linux system, but have just > added it. The city information does now include the offset from UT, but is > 1 hour fast everywhere, incl London, which should be UTC+0.0 , but shows > UTC+1.0 ; I think this has got something to do with the Daylight Savings strategy, because when I checked for some places where daylight savings method is not implemented (for example, India and Sri Lanka), the time zone displayed was correct.
Yes, it seems to believe we have summer time (daylight-saving time) in Toronto & London now ! It should use the info in 'timezone-data', but gets it wrong. This is a bug, which needs fixing. Is this something you are skilled enough to fix yourself ? If so, please add a patch to this bug.