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

From "colour" to "color"; i.e. to US english #21752

Closed
jm58660 mannequin opened this issue Oct 23, 2016 · 10 comments
Closed

From "colour" to "color"; i.e. to US english #21752

jm58660 mannequin opened this issue Oct 23, 2016 · 10 comments

Comments

@jm58660
Copy link
Mannequin

jm58660 mannequin commented Oct 23, 2016

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

@jm58660 jm58660 mannequin added this to the sage-7.5 milestone Oct 23, 2016
@jm58660 jm58660 mannequin added c: documentation labels Oct 23, 2016
@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Oct 23, 2016

Branch: u/jmantysalo/color-colour

@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Oct 23, 2016

Commit: c346d2c

@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Oct 23, 2016

New commits:

c346d2cChange colours to colors.

@jm58660 jm58660 mannequin added the s: needs info label Oct 23, 2016
@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Nov 23, 2016

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.

@jm58660 jm58660 mannequin added s: needs review and removed s: needs info labels Nov 23, 2016
@pjbruin
Copy link
Contributor

pjbruin commented Nov 23, 2016

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.

@fchapoton
Copy link
Contributor

comment:5

Replying to @pjbruin:

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.

Same opinion. I vote for duplicate/invalid.

@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Nov 23, 2016

comment:6

OK, but what you think about

class Color(object):
     def __int__(self):
         """
         Return the integer representation of this colour.

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.)

@pelegm
Copy link
Contributor

pelegm commented Dec 1, 2016

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 g.find_colors together with g.colourful should definitely be unacceptable, but docstrings with GB spelling, even if the function name is in US spelling, is fine with me.

(It is perhaps not super-aesthetic; but I guess we can live with it)

@jm58660
Copy link
Mannequin Author

jm58660 mannequin commented Dec 1, 2016

comment:8

OK.

@jm58660 jm58660 mannequin removed this from the sage-7.5 milestone Dec 1, 2016
@pjbruin
Copy link
Contributor

pjbruin commented Dec 1, 2016

Reviewer: Peter Bruin, Frédéric Chapoton, Peleg Michaeli

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

No branches or pull requests

4 participants