Yes, same behaviour with Italian time. Not sure if 12 or 24 or both mode.
I still have to take a look at the J code (I guess on weekend Ill' take a look) but I presume is just a trivial error easily fixable.
When I tried the Dbus road I read somewhere someone complain about time setting (12/24 connected to home config) and Qgil answering that was a low priority and never fixed... Maybe is related to that.
Anyway I would love to see a real integration with the 'nokiaclock' settings (does not seem right to try to duplicate an OS feature), have the small clock on status bar and the list of alarms on the nokia alarm list but im not sure if that is really possible (lack of docs and I think nokia close source fot their cr*p).
Im never been happy with the Dbus alarm thing; it never seem reliable enough: on paper the OS solution is the best possible but I feel there are just too many variable out of control: and launching the HUGE 3mb python just for make the thing hopefully playing is a recipe for disaster.
J is making a great works and probably a lot of this issue will just disappeared with new hardware and new OS, so is probably the right road for the official app. But that dont fit my need : Ill keep developing a parallel version where every variable the user see is what is going to happen and try to avoid as much OS traps as I can. The OS infrastructure on the actual tablets are so minimal that TO ME is often just easier replace with custom solutions (windows managments, requests, dialogs, etc). Obviously I just like doing it and is a waste of energy + bring really few contribute to the general maemo scene but is just my itch and I m glad maemo still host my python rantles.
Now is better grab some lunch and prepare for final week days rush