I am quite sure I'm not the only one that read the text with a brit accent in my mind.
No, I think a lot of us Brits do that too
The Queen’s stylesheets
21–30 of 74 posts
Re: The Queen’s stylesheets
#22I am going to put this into our development workflow.
It totally made my day. Thank you so much!
I admit that background music is highly relevant.
However, using 'photograph' => 'image', is not good. I suggest 'picture' => 'image', since it covers both illustrations and photographs.
Re: The Queen’s stylesheets
#23Smashing! Next order of business: i18n whereby .com becomes .co.us and .co.uk becomes .com?
That would be not politically correct. Instead .com-s have to be redirected to co.uk and co.us respective to their geography, and in 3 years course, .com TLD has to be abandoned in favour of equality rights. Long live the Queen.
Re: The Queen’s stylesheets
#24Your 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"
Funny enough, the example is ambiguous since: "transparency: 0.5" == "opacity: 0.5"
Yeah, when I caught that, I thought that it might just be semantic trolling! (a terrible variant)
Re: The Queen’s stylesheets
#25Not 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…
Indeed. They also forgot 'quite' => 'text-transform' ;)
Whose fault is it is British folks aren't the majority in W3C or even none of the British companies manufacture browser who implement the CSS specs. Hence, words are spelled like they are in America.
Re: The Queen’s stylesheets
#26Your 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"
Funny enough, the example is ambiguous since: "transparency: 0.5" == "opacity: 0.5"
ooohh, devious!
Re: The Queen’s stylesheets
#27I guess we also need ones for other languages
透明度: 0.5;
色: 紫;
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 only it's English only. I don't know other languages but I suspect the suffix 'er' has no meaning in Spanish, Italian, French, and that being forced to added it to classes written using those languages would really suck.
type Escribirer interface // !?!?Re: The Queen’s stylesheets
#28auto playing music on the web is a bit 90s no?
Indeed, it puzzles me why people still enable it in their browsers.
Re: The Queen’s stylesheets
#29The sound. Oh my goodness, the sound. Why is there not a button to stop it? I was listening to some music in the background with multiple tabs open, and I didn't expect a project link from HN to autoplay music. Confusion ensues.
http://www.youtube.com/embed/yHNfvJc99YY?fs=1&autoplay=1... style="width: 400px; height: 400px; position: absolute; left: -999em; top: -999em; visibility: hidden; -webkit-user-select: none; -webkit-user-drag: none;" frameborder="0" allowfullscreen>
Re: The Queen’s stylesheets
#30Not 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.