Breakout thread from Feature Request: Excise multiple types In UI for Once And All
Proposal: renaming APIs such as juce::Colour to their American spellings, e.g. juce::Color.
If a member of the community could make an extensive list of identifiers using British spellings, this would help with understanding the amount of work required.
How do we count the number of people who don’t want to go through the effort required to change their code bases to “fix” this ridiculous “problem”?
Another “feature” request : “Keep the British spellings just as they are”?
A proxy vote by number of “likes” on this comment?
British spellings are perfectly legitimate given the heritage of the project.
I believe it is still developed in the UK. Being British myself, I quite like it as most SDK’s forget about our spellings. CSS gets me every time with “color” when developing my website…
For sure, I can’t imagine a greater invest of developer time than fixing breaking changes in our 15 active JUCE-based products because of spelling changes in the JUCE codebase with the next major JUCE update 
To avoid to be confused all the time i use the “Colour” spelling from the beginning in all my projects.
It would be a huge work to change/grep to “Color” for me now. 
For what?
I can’t think of a bigger waste of time for JUCE devs to be getting involved in …
Just leave it. Deal with it, Americans.
I’m American, and I don’t have a problem with it. 
American also, and I have no problem with it. In fact, the spellings are a mnemonic to associate the functions. They make you think about it,…which is a good thing.
+1 for keeping things the way they are.
If it ain’t broke, don’t fix it!
This would break a huge amount of code bases, and have essentially zero benefit (also speaking as an American).
Didn’t someone submit this as an April Fools’ joke a few years ago?
