|
A user reported bug 5196, saying "When setting the time for an event
[in a locale that uses AM/PM], "military" time is not recognized": https://bugzilla.osafoundation.org/show_bug.cgi?id=5196 Proposal #1: Mimi suggested a strategy for guessing which the user meant: - if that time didn't previously have a value (eg, the user replaced the "hh:mm AM" hint), use AM if the hour < 13, else PM. - Otherwise, use the AM/PM from the previous value. Proposal #2: Slightly more complicated than Proposal #1, which has weirdness if the previous value was 12:00 PM (which is noon), changing it to 11:45 would move it to almost midnight. Instead: - if that time didn't previously have a value (eg, the user replaced the "hh:mm AM" hint), use AM if the hour < 13, else PM. - Otherwise (previous time had a value!), if the previous time was exactly 12:00 PM (noon), use AM. (This doesn't fix weirdness around midnight, but that'd be less of an issue and harder to guess; think about it.) - Otherwise, use the AM/PM from the previous value as is. Proposal #3: Don't do any guessing: reject the value as incomplete... because Mimi also suggested that guessing might be confusing to users who aren't thinking in terms of a 24-hour clock. (We already provide autocompletion as the user's typing anyway, and it does the right thing) Don't vote yet. If you think we should use a different strategy than one of these, please propose it now. I'll call for votes in a few days. ...Bryan |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
