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
From "colour" to "color"; i.e. to US english #21752
Comments
Branch: u/jmantysalo/color-colour |
Commit: |
New commits:
|
comment:3
Got no interest about US/GB -issue. So I just mark this colour->color as needs_review. Please review, either to milestone sage-7.5 or to milestone wontfix. |
comment:4
I disagree with enforcing a particular spelling. Both are perfectly acceptable, and permitting both has absolutely no effect on readability. I just expect people who use one variant to get annoyed by others "correcting" their spelling to the others' preferred variant. |
comment:5
Replying to @pjbruin:
Same opinion. I vote for duplicate/invalid. |
comment:6
OK, but what you think about
or like? Fortunately we have only one form used as keyword or function name. I suppose that you wouldn't like them to have different spelling. (You can be sure that I have no personal preference of which one to use. My native language is quite far from english.) |
comment:7
I vote for invalid. I think that code (methods, functions, classes) should all follow US English (this is just far too common in CASs so far; and it should be consistent), so for example (It is perhaps not super-aesthetic; but I guess we can live with it) |
comment:8
OK. |
Reviewer: Peter Bruin, Frédéric Chapoton, Peleg Michaeli |
This patch will change some colours to colors.
The real question is larger: shall we add "Use US english" to the developer manual? I think that we should. (I have no prefence, but US english is currently more used.)
CC: @jdemeyer @tscrim @fchapoton
Component: documentation
Author: Jori Mäntysalo
Branch/Commit: u/jmantysalo/color-colour @
c346d2c
Reviewer: Peter Bruin, Frédéric Chapoton, Peleg Michaeli
Issue created by migration from https://trac.sagemath.org/ticket/21752
The text was updated successfully, but these errors were encountered: