Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

BritCSS: Fixes CSS to use non-American English

github.com

Post reply on HN
Print view View original

11–20 of 180 posts

Re: BritCSS: Fixes CSS to use non-American English

#14

Post by jsheard »

sebmellen wrote: post #13
jsheard wrote: post #11

HTTP had the right idea, just get the spelling completely wrong so everyone gets equally pissed off. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re...

Hilarious. I feel like referer looks correct now, having seen it so often.

Except now there's also the "Referrer-Policy" header, which is spelled correctly. I wonder if the spec committee debated calling it Referer-Policy for consistency.

Re: BritCSS: Fixes CSS to use non-American English

#17

Post by FlamingMoe »

troad wrote: post #7
kibwen wrote: post #6

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

Obliged to point out that spelling is always an entirely cultural artefact, and that before colour was spelt color, it was spelt colos. There's nothing more correct about older forms, or newer forms, or any other forms. What matters is what is going to be clearest to your speech community and audience.

However, that is not the perspective of the creator of BritCSS, who refers to current CSS property names as "bastardised" spellings.

Re: BritCSS: Fixes CSS to use non-American English

#18

Post by troad »

FlamingMoe wrote: post #17
troad wrote: post #7

Earlier quoted context omitted.

Obliged to point out that spelling is always an entirely cultural artefact, and that before colour was spelt color, it was spelt colos. There's nothing more correct about older forms, or newer forms, or any other forms. What matters is what is going to be clearest to your speech community and audience.

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 much a cherished part of their cultural inheritance as yours is to you.

Re: BritCSS: Fixes CSS to use non-American English

#20

Post by DrammBA »

troad wrote: post #18
FlamingMoe wrote: post #17

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…

[flagged]
Post reply on HN