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

Format the ahead/behind count in a locale-aware manner #1245

Open
joshaber opened this issue Apr 20, 2017 · 7 comments
Open

Format the ahead/behind count in a locale-aware manner #1245

joshaber opened this issue Apr 20, 2017 · 7 comments
Labels
electron Issues related to our use of Electron that may need updates to Electron or upstream fixes enhancement

Comments

@joshaber
Copy link
Contributor

screen shot 2017-04-20 at 3 03 30 pm

That should be 61,083 in 🇺🇸 and probably something else in other places.

@shiftkey
Copy link
Member

Seems legit:

var number = 10000
number.toLocaleString()

@shiftkey
Copy link
Member

As discussed in #1257, we should fix this properly. See electron/electron#9247 for the upstream issue and #1257 (comment) for some further context.

@shiftkey
Copy link
Member

This idea is interesting for the future, but this is beyond the scope of our current roadmap.

I added the future-proposal label to this issue and closed it so that we won't get overwhelmed with our backlog! We will revisit this in our next planning session.

@iAmWillShepherd
Copy link
Contributor

Reopening this issue now that electron/electron#15035 exists. We should be able to get a proper fix once it lands and we update electron.

@shiftkey shiftkey added electron Issues related to our use of Electron that may need updates to Electron or upstream fixes and removed future-proposal labels Oct 12, 2018
@j-f1
Copy link
Contributor

j-f1 commented Oct 16, 2018

In #5914, @cheshire137 suggested using a “k” suffix, which would eliminate the need for locale-specific formatting.

@shiftkey
Copy link
Member

shiftkey commented Apr 9, 2019

Reopening this issue now that electron/electron#15035 exists. We should be able to get a proper fix once it lands and we update electron.

Bumping this to indicate it's currently only available in Electron 5 (currently in beta), and if it's more urgent we'd need to investigate whether we could backport the work to Electron 4.x. My gut feeling is that we can wait until we upgrade to Electron 5, but happy to discuss further...

@j-f1
Copy link
Contributor

j-f1 commented Apr 9, 2019

I think it’s not too urgent because (a) commits don’t come in fractions and (b) it’s likely users from countries that use commas as decimal points will have some familiarity with the use of periods, so they’d get the message. Another alternative is to switch to spaces (“61 083”) although I’m not sure how familiar the general population is with that format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
electron Issues related to our use of Electron that may need updates to Electron or upstream fixes enhancement
Projects
None yet
Development

No branches or pull requests

4 participants