Earlier quoted context omitted.
However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.
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…
BritCSS: Fixes CSS to use non-American English
61–70 of 180 posts
Re: BritCSS: Fixes CSS to use non-American English
#62Wach an US movie, then watch a British movie. Compare TV shows, compare news articles.
Re: BritCSS: Fixes CSS to use non-American English
#63Earlier quoted context omitted.
I think it's a play on the Chinese language having Traditional/ Simplified versions. I'm choosing to take this repo as tongue-in-cheek, which is hard to really determine online...
I want to see it as tongue-in-cheek as well, but, I feel like that's a stretch...what would be the humor in that? But even if it doesn't make sense to me, I prefer your interpretation of motive.
Re: BritCSS: Fixes CSS to use non-American English
#64Always funny to poke a little fun at ourselves.
Re: BritCSS: Fixes CSS to use non-American English
#65Earlier 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
#66Earlier quoted context omitted.
However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.
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…
Re: BritCSS: Fixes CSS to use non-American English
#67I believe that some people's actual full-time job is to translate software from US English to British English. I wonder what that job feels like after the thousandth time you've replaced color with colour and neighbor with neighbour
Re: BritCSS: Fixes CSS to use non-American English
#68I believe that some people's actual full-time job is to translate software from US English to British English. I wonder what that job feels like after the thousandth time you've replaced color with colour and neighbor with neighbour
As a programmer working in the UK I've never been asked to rewrite something into British English. I have been instructed to convert some old codebase to American spellings to "avoid confusion". Probably about 6 times in 20 years of professional programming and usually by some product manager based in San José following an acquisition. This is why the library exists I expect.
Re: BritCSS: Fixes CSS to use non-American English
#69Why does the author use `initialize` for a function name in the source code? I question their purity of intentions!
Seriously, -ize endings in the Cambridge spelling tradition relies on you knowing the etymology of the word, and if it’s from the Ancient Greek, that’s the one you use. Otherwise -ise for French or Latin words.
Re: BritCSS: Fixes CSS to use non-American English
#701. All of this could have been avoided but for the want of some MPs for some colonies. But no. 2. "License: Not Specified" instead of "Licence: Not Specified"