Bug 1576 - time format settings are confusing when a time under 13:00 is displayed
: time format settings are confusing when a time under 13:00 is displayed
Status: CLOSED FIXED
Product: MySqueezebox.com
Classification: Unclassified
Component: Player UI
: unspecified
: All All
: P2 normal (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-18 12:42 UTC by Kevin Pearsall
Modified: 2008-12-15 12:13 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-05-18 12:42:50 UTC
it's showing as possibilities:
12:35 pm
12:35
12.35
12,35
12h35
12:35 pm
12:35
12.35
12,35
12h35

It's repeating a list of 5 twice...  Are the last 5 supposed to be 24h?  if so,
this should be messaged some other way like...

12:35 pm
12:35 (12 hour)
12.35 (12 hour)
12,35 (12 hour)
12h35 (12 hour)
12:35 pm
12:35 (24 hour)
12.35 (24 hour)
12,35 (24 hour)
12h35 (24 hour)
Comment 1 Vidur Apparao 2005-05-19 14:17:34 UTC
It turns out that this is the actual list:

12:35 pm - hh:mm pm (12h)
12:35    - hh:mm (24h)
12.35    - hh.mm (24h)
12,35    - hh,mm (24h)
12h35    - hh'h'mm (24h)
12:35 pm - h:mm pm (12h)
12:35    - h:mm (24h)
12.35    - h.mm (24h)
12,35    - h,mm (24h)
12h35    - h'h'mm (24h)

The first set is identical to the second set, except for the leading 0 if the
hour is a single digit. I think Dave got this list from SlimServer. Seems pretty
redundant, so I'm tempted to get rid of the entire second set...or consider a
better list.
Comment 2 Blackketter Dean 2005-06-07 20:48:00 UTC
Let's leave the full list there.  Some foreigners are very touchy about their time/date formats.  sheesh. :)
Comment 3 Kevin Pearsall 2005-06-14 10:31:37 UTC
ok well could the strings at least be changed so that it makes more sense?  like
the strings vidur put in comment #1?
Comment 4 Vidur Apparao 2005-06-15 16:31:45 UTC
Fixed in next push out of service.
Comment 5 James Richardson 2008-12-15 12:13:46 UTC
This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.