AM/PM vs 24 hours not used consistently

RESOLVED FIXED

Status

RESOLVED FIXED
17 years ago
12 years ago

People

(Reporter: gullc, Assigned: mikeypotter)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

17 years ago
I'm using RC1, Win 2000, Calendar of May 5th.

I remember that there was once a discussion about being able to choose the 24 h
system instead of the American AM/PM system. I don't know how far it has been
implemented, but there are at least two places where the calendar is not
consequent (view also attachement):

the day week view show AM/PM time
the time picker popup shows 12 hours to choose plus AM/PM (so far everything's
ok...)

the start/end time in the event editor use the 24 h system (my computer actually
shows 16:00 for 4 PM).
I don't know about the event view, as it doesn't work right now, but if I
remember it right it also used the 24 hours system.

I would like to see the time in the 24 hours system in day/week view and I'd
like to be able to 'pick' it using the 24 hours system.
If that's not going to be implemented for now, I'd like to have my time in AM/PM
everywhere rather than half of it in AM/PM, half in 24.
(Reporter)

Comment 1

17 years ago
Created attachment 82521 [details]
A screen shot.

Comment 2

17 years ago
Assuming consequently=consistently and confirming based on screenshot.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: AM/PM vs 24 hours not used consequently → AM/PM vs 24 hours not used consistently
(Reporter)

Comment 3

17 years ago
Yes, I meant consequently. Sorry for my bad English...
(Assignee)

Comment 4

17 years ago
I have fixed this in the day and week view.
The time picker is going to be redone, so that will get fixed when that happens.
I'll mark this bug as fixed now, even though not all the issues are addressed.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
The bugspam monkeys have been set free and are feeding on Calendar :: Sunbird Only. Be afraid for your sanity!
QA Contact: colint → sunbird
You need to log in before you can comment on or make changes to this bug.