Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize capitalization to am/pm, for message-list #966

Merged
merged 1 commit into from
Jan 20, 2016

Conversation

cllns
Copy link
Contributor

@cllns cllns commented Jan 12, 2016

The time format for closed vs. expanded in the message-list is not consistent.
Closed:
screen shot 2016-01-11 at 17 06 13

Expanded:
screen shot 2016-01-11 at 17 06 19

A number of other things change, but if the time format is the same, it'll appear as though the only thing changing with the time is adding the date before it.

This patch fixes that.

I have no opinion on lowercase vs. uppercase. Switching it to lowercase was just an easier change.

@bengotow
Copy link
Contributor

Hey @cllns — this looks great, thanks for the fix! How do you feel about am/pm vs AM/PM? I looked at a couple other Mac apps for comparison (Mail.app and Evernote), and they seem to capitalize them everywhere. Maybe we should standardize them in the other direction?

@cllns
Copy link
Contributor Author

cllns commented Jan 15, 2016

I think AM/PM is more natural than am/pm, but I also kind of like the lowercase aesthetically. It's different, for sure, but it also kind of goes with the feel of N1.

Maybe a designer at @nylas can chime in?

@bengotow
Copy link
Contributor

Hey @cllns — we've decided to standardize on AM / PM (capitalized). Want to update this pull request real quick and we'll land it? Thanks!

@cllns cllns force-pushed the standardize-am-and-pm-capitalization branch from b8ed9d3 to f14087a Compare January 19, 2016 22:54
@cllns
Copy link
Contributor Author

cllns commented Jan 19, 2016

All set @bengotow!

@bengotow
Copy link
Contributor

Thanks—welcome to the project! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants