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

51–60 of 180 posts

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

#51

Post by kennysoona »

_nivlac_ wrote: post #48
kennysoona wrote: post #46

Kind of funny the animus the author has against US spellings. It's nothing but shade to refer to US spellings as 'simplified' and UK spellings as 'traditional', regardless of the merit of the argument for doing so. I can't imagine anyone will really need to use this, but it seems to have let the author work out some issues.

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

#52

Post by kennysoona »

_blk wrote: post #50
kennysoona wrote: post #46

Kind of funny the animus the author has against US spellings. It's nothing but shade to refer to US spellings as 'simplified' and UK spellings as 'traditional', regardless of the merit of the argument for doing so. I can't imagine anyone will really need to use this, but it seems to have let the author work out some issues.

Arr, only pirrates have trru spellingg LC_ALL=en_PR

I guess ninjas also since they use pirate spelling as well.

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

#53

Post by jasonjei »

kennysoona wrote: post #46

Kind of funny the animus the author has against US spellings. It's nothing but shade to refer to US spellings as 'simplified' and UK spellings as 'traditional', regardless of the merit of the argument for doing so. I can't imagine anyone will really need to use this, but it seems to have let the author work out some issues.

The funny thing about references to Traditional Chinese (HK and Taiwan) and Simplified Chinese is that there’s even more shade in Chinese…

簡體字（简体字）Simplified characters

繁體字（繁体字）Complicated characters

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

#54

Post by nine_k »

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.

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.

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

#55

Post by k1t »

dullcrisp wrote: post #35
k1t wrote: post #22

Earlier quoted context omitted.

Personally, I would have, since it refers to the Referer header it seems like it should follow the same spelling. It would be like CSS having a "color" attribute, but then doing something like "default-colour".

It’s actually more like CSS having a “colr” attribute and then doing something like “default-color”.

I think that depends on whether or not you consider 'color' to be the correct spelling? :)

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

#56

Post by 0tfoaij »

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 Latin -or words were often spelled with -or, -our, and -ur in Old French also. If you are using Wiktionary as a source you have to click through to the Old French definitions to see the alternate forms, as well as parsing the descendant table to see the derived forms that the simple etymology blurb often leaves out. Doing so you can also see that Middle Dutch has 'coleur' (modern kleur) which very likely did not originate from Middle French given the timeframe.

The earliest quotations for colour in the Oxford English Dictionary are from around 1300 where it was spelled 'colur' (cf Welsh) which while being post-Norman England is not post-Norman English. For Norman/Angevin-England the OED also has a quotation for honour as 'onur' listed as before 1200 (and again as 'onour' from around 1300). If you want to make a case of superfluous 'u's being added a better example would be something like chancellor, where the 'u' was added in Middle English and then later removed, rather than colour (or honour) where the 'u's have existed since the earliest quotations. The reason color and honor stuck about in English is most likely because that is how they were spelled in Latin.

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

#57

Post by mattl »

hsbauauvhabzb wrote: post #8

This creates a second language where two dialects that have minor differences meaning stackoverflow code won’t always work, nor will code you extract from other websites. This creates a mess, all while adding a JavaScript pre-processor that is prone to have errors, vulnerabilities and other flaws from the NPM hellscape. No thanks.

I mean, yes but this is also a joke.

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

#58

Post by pwdisswordfishz »

_blk wrote: post #50
kennysoona wrote: post #46

Kind of funny the animus the author has against US spellings. It's nothing but shade to refer to US spellings as 'simplified' and UK spellings as 'traditional', regardless of the merit of the argument for doing so. I can't imagine anyone will really need to use this, but it seems to have let the author work out some issues.

Arr, only pirrates have trru spellingg LC_ALL=en_PR

Puerto Rican English? Does it differ that much from mainland US variety?
Post reply on HN