-
Notifications
You must be signed in to change notification settings - Fork 627
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
Language (i.e. US English) #26
Comments
interesting point ... I give a +1 for US English ... I could never figure out why do we need a "u" in color |
So that it is spelt correctly :-P |
I don't think I can be friends with Marin anymore! ;] I think the writing guide already says something about US English so it probably makes sense here too. Also to be consistent with |
@ColinEberhardt I think "spelt correctly" is defined by which spell checker you have on :) Anyways ... @gregheo makes a great comment there - UIColor and NSColor (ehm, also SKColor) are already using US spelling |
Agreed. It looks odd to do this:
Or at least to a newcomer, for whom English is not their first language, it adds cognitive load that they don't need. |
I find spelling to be a considerable cognitive load ;-) and I'm a +1 vote for the leftpondian version of English. |
+1 for US English for the sake of consistency. |
+1 for US English (good think Mike Daley isn't here, I don't think he'd let this go w/o a fight! ;]) |
+1 for US English. +1 for the comment about Mike Daley 😉 |
+1 for US English (weird thing that @micpringle isn't watching careful enough to edit Ray's "good think") |
@icanzilb It was a test. You passed 😉 |
sweet! |
I couldn't find any mention of what language we should use. I know it's slightly pedantic, but I think it should be explicit that methods, variable names etc use a standard choice of language. Presumably we'd pick US English.
It only really matters in things like color vs colour, recogniser vs recognizer, etc.
Thoughts?
The text was updated successfully, but these errors were encountered: