BritCSS: Fixes CSS to use non-American English
131–140 of 180 posts
Re: BritCSS: Fixes CSS to use non-American English
#132Earlier quoted context omitted.
However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.
I mean, wouldn't the U.S as a nation essentially be a bastard child of Britain, and thusly use a bastardized English?
Re: BritCSS: Fixes CSS to use non-American English
#133Obliged to point out that "color" is how it's spelled in Latin, Old French, and therefore post-Norman English, that the superfluous "u" was added later by the English aristocracy because they were jealous of how fancy the newly-respelled French looked.
It's additionally funny that in French, "ou" reads as [u], that is, approximately like the wovel in "fool" (cf "jour", "amour", "troubadour", etc). I wonder if it was actually pronounced like "coloor" at any time in the past.
https://en.wiktionary.org/wiki/colour#Middle_English
The second vowel, /uː/, is like in "true". (Note also the range of alternate spellings: colur, color, culur, coler, coloure, kolour.)
Re: BritCSS: Fixes CSS to use non-American English
#134Earlier quoted context omitted.
However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.
It's fair to assume that if a brit writes something online, it's highly likely to be a piss take joke. We just don't waste our time writing /s on the end of every sentence
Re: BritCSS: Fixes CSS to use non-American English
#135Obliged to point out that "color" is how it's spelled in Latin, Old French, and therefore post-Norman English, that the superfluous "u" was added later by the English aristocracy because they were jealous of how fancy the newly-respelled French looked.
However I think that when Americans brought it back they missed opportunity to get rid of 'c' and put 'k' there instead. Is 'c' even used in English language? It usually is just 'k' or 's'.
Re: BritCSS: Fixes CSS to use non-American English
#136The reason css properties have a standardized spelling is not to make fun of british spelling, but to have a standard that everyone could follow for interopabilitys sake.
If youre such a british language purist that you go this route, you will need to port/retrofit this hack to your future projects or you will once more have to debug why ”colour” doesnt do anything in your css declaration.
This is anti progression and a non-solution.
In addition, running this hack on the client side (really, why??) has additional downsides as color wont render right until after page load.
A solution for this non-issue would be scss preprocessor variable, something like this:
$colour = ”color”
table {
$colour: red;
}
TLDR: css is a standard, so learn it and work with it, not against it.Re: BritCSS: Fixes CSS to use non-American English
#137Re: BritCSS: Fixes CSS to use non-American English
#138This should be paired with British PHP ( https://aloneonahill.com/blog/if-php-were-british/ )
Re: BritCSS: Fixes CSS to use non-American English
#139Calling British English (also known as just English) 'non-American English' is like calling an original a 'non-duplicate'. American is basically English with typos, bad grammar, and bad style.
Re: BritCSS: Fixes CSS to use non-American English
#140Earlier quoted context omitted.
S/he's wrong, simple as that. "The particular spatio-temporal version of speech that I grew up with is correct, and all others are bastardised" is not a defensible or - frankly - interesting position. Chaucer would find virtually all modern English to be debased; Bede would wince at Chaucer's English; and so on, forever. Nothing fruitful comes from cultivating arrogance towards the language of others. It is just as m…
your wrong