> Yes. And for most folks that's fine, they're not looking for IMs that > are over 12 hours old so having it be close to the time that they're in > is fine.
I'm one of the folks who's not fine with it. It's simply directly un-useful for me to have to convert timestamps from 12h to 24h when I receive IMs. The information should be communicated to the user in a way consistent with their locale, and timestamps in particular should not be difficult to write correctly. You should not and do not need to have .po files or whatever for your format strings for every single language to find the information you need to present such information correctly. Short version of the above: Marking this as "wishlist" is arrogant. Please reconsider. -- Timestamp in messages not consistent with desktop https://bugs.launchpad.net/bugs/334036 You received this bug notification because you are a member of Indicator Applet Developers, which is the registrant for Indicator Applet. Status in Indicator Applet: Confirmed Bug description: When I come back to my PC and I have queued messages up they read like this: [ICON] Ken VanDine 03:58 My clock says 15:58, I think that the timestamp should follow whatever time-format the user has defined in their settings. So if it's normal 12 hour time it should say 3:58pm or whatever without the leading zero. I had to think for a second on what that number was until I realized it was the time the message was sent to me. _______________________________________________ Mailing list: https://launchpad.net/~dx-team Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-team More help : https://help.launchpad.net/ListHelp
