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

Determine Spelling and grammar conventions #16

Open
ericpoe opened this issue Feb 10, 2019 · 2 comments
Open

Determine Spelling and grammar conventions #16

ericpoe opened this issue Feb 10, 2019 · 2 comments

Comments

@ericpoe
Copy link
Contributor

ericpoe commented Feb 10, 2019

This project's history centers around the UK. As such, spelling and grammar conventions follow those of the UK. For instance: 'licence' (UK) vs "license" (US); single-quotes (UK) vs Double-quotes (US).

I propose that, based on this project's history and this project's leadership from many corners of the globe, that we continue following UK-based spelling and grammar rules.

In either case, we need to have some way of enforcing US or UK spelling/grammar rules.

@iansltx
Copy link
Contributor

iansltx commented Feb 10, 2019

So, the original builder of the project, going all the way back, was a mix of Chris Cornutt (US) and Lorna (UK), with Chris being the initial creator.

As such, there's precedent for the project adopting the conventions of the country where the primary contributors reside. Since the new project team is primarily US-based, it makes sense to, in cases where we can't (or don't yet) locali(s|z)e, push back toward US conventions as items are touched for other reasons.

Otherwise you have to give folks a history lesson when they ask why the site adopts the default locale that it does.

(and if we were in a situation where the shepherding organization was in Europe rather than the US, I'd be arguing to enshrine en-GB for the exact same reasons).

@heiglandreas
Copy link
Member

heiglandreas commented Feb 10, 2019

There currently is a default locale which is en-GB. It might not be enforced all over the place but it is still existent. So why do we have to change it?

I'd even go one step further and ask: Why do we have to decide on one or the other? So far en-UK and en-US were both used and it hasn't harmed the project. It might look unfamiliar to some but is it really necessary to be a) defined and b) enforced?

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

No branches or pull requests

3 participants