Live data from Hacker News

The Queen’s stylesheets

spiffingcss.com

31–40 of 74 posts

Re: The Queen’s stylesheets

#33

I guess we also need ones for other languages 透明度: 0.5; 色: 紫; which does bring up the point, are we being at all culturally insensitive by making nearly all web standards English? Or how about UsingCamelCase? Give than some languages don't have the concept of UPPER/lower case. Does Go require you to use "er" for interfaces as in Writer, Reader, Serializer? That seems even worse given that it not just roman letters on…

The thing about English use is, well, at least it is consistent. Everything uses American English, so if you need to learn to program, there is only one language to learn. Allowing other languages wouldn't solve much since English would still be present in all the API methods and so on, so I think consistency is better.

Re: The Queen’s stylesheets

#34

Not very many substitutions performed[1]: 'colour' => 'color', 'grey' => 'gray', '!please' => '!important', 'transparency' => 'opacity', 'centre' => 'center', 'plump' => 'bold', 'photograph' => 'image', 'capitalise' => 'capitalize' Would've thought there'd be a ton of opportunities to pedantically correct CSS's choice of words. !please instead of !important made me laugh, though. [1]: Taken from https://github.com/id…

Some are incorrect. Transparency and opacity are opposites.

Looks like an issue and pull request were filed for that:

https://github.com/idiot/Spiffing/issues/1

https://github.com/idiot/Spiffing/pull/7

Re: The Queen’s stylesheets

#36
post #7

I am quite sure I'm not the only one that read the text with a brit accent in my mind.

By "British accent" you probably mean Received Pronunciation or Queen's English... but there is more to Britain than the South East (we have the North, Scotland and Wales, plus plenty of regional accents).

Re: The Queen’s stylesheets

#37

I guess we also need ones for other languages 透明度: 0.5; 色: 紫; which does bring up the point, are we being at all culturally insensitive by making nearly all web standards English? Or how about UsingCamelCase? Give than some languages don't have the concept of UPPER/lower case. Does Go require you to use "er" for interfaces as in Writer, Reader, Serializer? That seems even worse given that it not just roman letters on…

Go does not require "er", and in fact most code I've seen outside the standard library doesn't seem to follow any particular convention for using it. If there /was/ such a convention, it would obviously make sense to use the closest equivalent suffix in the language.

Re: The Queen’s stylesheets

#38
post #4

Your example is incorrect "transparency: 1" != "opacity: 1" We use transparency in the US. Transparency is how much light passes through an object and Opacity is how much it blocks. so: "transparency: 1" == "opacity: 0"

If you ask what the difference is between ‘transparent’ and ‘opaque’, most people will answer correctly. If you append –y, people somehow get confused.

Re: The Queen’s stylesheets

#39
post #16

While the linguist in me is appalled by the author's joking (hopefully!) prescriptivist notion that British English is equivalent to such a thing as "correct English" (the American in me is also perturbed by such a claim), I'd like to point out that the home page's phrase "amount of features" is considered by such prescriptivists to be incorrect English. :) They would insist on "number of features" :P

A brief note to the Author of the Page in question

"...one must check whether one has PHP 5.2 (or newer) installed upon their Internet server..."

Should this not be 'one's Internet server'?

"Something our primitive stateside friends can understand"

What is this 'stateside' you speak of, Sir? Our Colonial Cousins may also resent the adjective that has been applied.

I personally rather regret the automatic recitation of Arne's ditty when visiting the page.

Post reply on HN