Skip to content
This repository has been archived by the owner on Feb 7, 2019. It is now read-only.

Update UX strings #163

Merged
merged 6 commits into from
Oct 16, 2017
Merged

Update UX strings #163

merged 6 commits into from
Oct 16, 2017

Conversation

devinreams
Copy link
Contributor

@devinreams devinreams commented Oct 11, 2017

Fast follow work from #154 related to #138

(will rebase to get this cleaned up)

@devinreams
Copy link
Contributor Author

@changecourse @sandysage Let's look at getting final strings in for Alpha. You'll see each file has some that we can swap out with little-to-no-work.

I took a first pass based on what's in Invision... (click "Files Changed" here to see)

@devinreams devinreams added this to the 0.1.0 - Alpha milestone Oct 11, 2017
@devinreams devinreams self-assigned this Oct 11, 2017
changecourse
changecourse previously approved these changes Oct 11, 2017
Copy link
Contributor

@changecourse changecourse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@ghost ghost added the in progress We are actively working on it. label Oct 11, 2017
@linuxwolf linuxwolf modified the milestones: 0.1.0 - Alpha, 0.1.1 Oct 16, 2017
Copy link
Contributor

@changecourse changecourse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not all instances of item are being captured, nor is the changes for "Entry Name" and "Website Address"

as seen here: https://mozilla.invisionapp.com/share/P6DT2HP8X#/256782988_1-0-3_Lockbox_Home_-_Entry_Detail_-_Add_Entry_-_Filled


homepage-no-passwords =
Welcome to Lockbox! I'm Lockie, and I'm here to help you lock
up your passwords!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure this will break things. The trailing whitespace is important for ensuring that fluent.js parses the entire body as one string.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Atom was overly helpful. Added back in next commit.

toolbar-go-home = Home
toolbar-send-feedback = Feedback

item-filter.placeholder = Filter…
item-filter.placeholder = Search for an Entry
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe the prevailing style in Firefox is sentence case, not title case.

[one] 1 item
*[other] { $count } items
[one] 1 Entry
*[other] { $count } Entries
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should also be sentence case, since it's not really a title (though this one is less clear, since button labels are title case in Firefox).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was basing the decision for title case off of the photon design guidelines, here: http://design.firefox.com/photon/copy/capitalization.html

item-summary-no-username = (no username)
item-summary-new-item = New Entry
item-summary-no-title = (No Entry Name)
item-summary-no-username = (No Username)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about title case here... Maybe we really just need some CSS to style these specially, like as italic or something?

Copy link
Contributor

@linuxwolf linuxwolf Oct 16, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've dealt with too much internationalization concerns elsewhere to not feel confident with CSS directives here (e.g., Turkish dotless i). Maybe I shouldn't be so concerned, but I'd rather start with the strings matching the mockups directly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's fine; I was just thinking about greying them out a bit or something to indicate that they're not human-entered.

Copy link
Contributor

@linuxwolf linuxwolf Oct 16, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The italics or color change seems like something we can follow up on ... this text matches the invision mockup + how @changecourse (and I) interpret the Photon guidelines.

@linuxwolf linuxwolf modified the milestones: 0.1.1, 0.1.0 - Alpha Oct 16, 2017
@linuxwolf
Copy link
Contributor

@jimporter @changecourse latest commit should address your concerns ... would you confirm?

@linuxwolf linuxwolf merged commit e351eae into master Oct 16, 2017
@ghost ghost removed the in progress We are actively working on it. label Oct 16, 2017
@linuxwolf linuxwolf deleted the update-ux-strings branch October 16, 2017 21:37
@devinreams
Copy link
Contributor Author

devinreams commented Oct 16, 2017 via email

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

Successfully merging this pull request may close these issues.

4 participants