I’ve definitely heard Araucaria araucana called “monkey puzzle” quite often in English, and many people in Australia mistakenly call the bunya pine (Araucaria bidwillii) “monkey puzzle” as well because they are closely related species and look fairly similar (I’m from Australia). There are several species of Araucaria in Australia though, so many people would also be aware of the Norfolk Island pine (Araucaria heterophylla) and probably the hoop pine (Araucaria cunninghamii). I think some people who are familiar with the different species would probably understand that if you said “Araucaria” you would be probably be referring to Araucaria araucana.
I’m not sure if you’re joking (sorry), but a ‘crowned republic’ [0] is definitely a common way to characterise the effective political system of many constitutional monarchies today — in particular the UK, Australia, Canada, and New Zealand.
This will happen in most browsers (I’m on Safari 14, macOS 11.2). The popup-blockers in most browsers will allow a popup if it is opened directly because of user input, such as a button click — a fairly simple measure which can be implemented by only allowing certain APIs to work within an event handler, for example.
There are a few Web APIs which work this way — for example, you can’t make a page fullscreen unless you do so in response to user input/interaction [0].
You’re right, I was mistaken (and too late to edit my comment).
Out of interest, is there a page anywhere explaining the difference between RustEnhanced and Sublime-LSP + Rust Analyzer? I’ve got both installed, but when I enable Sublime-LSP + RustAnalyzer the experience and functionality is different enough that I assumed it was overriding RustEnhanced.
I would assume that’s entirely possible, but something like this could be done using the HTML5 <video> or <audio> elements for video or audio codecs (there’s even a DOM API to do it! [0]), and some browsers advertised WebP support via the HTTP Accept header [1]. For tracking, I’d assume it’s not very useful these days apart from determining who’s using Safari?
Edit: Not to mention that the onerror event handler on the <img> tag has always been able to find out if an image didn’t display [2].
> I'd like to support it in my own websites, but I literally can't since a huge chunk of visitors use Safari.
Wouldn’t using the <picture> element[0] allow this this? It’s pretty widely supported (every browser that supports WebP and Safari)[1] and allows a fallback to a JPEG in an <img> tag.
I’d say compared to other languages there’s been two big issues:
1. A not insignificant number of packages are either polyfilling things in browsers, or providing a consistent (or ‘isomorphic') API for certain things across both browsers and Node.js, or adding things that should have been in a standard library.
2. A lot of packages still seem to be distributed primarily as CommonJS and not ES Modules. CommonJS makes tree-shaking harder than it should, so it was often just easier to break what should have been a single library into many smaller pieces.
Hopefully in the not too distant future library maintainers get around to reading the Node.js docs[0] fix some of this.
Sadly it seems to be out of print, but Bob Woolmer’s posthumously published Art and Science of Cricket[0] is an incredibly expansive and throughly researched study of cricket as a sport. It seems to have been really difficult to translate the physics of cricket into actionable things for players, but this book is in my opinion the best attempt.
This map seems to use a very variable and at times generous definition of both “company” and “still in business”.
Sure, Australia Post is one of Australia’s oldest institutions if you count from the date of the establishment of its oldest predecessor (which this map does, as a Postmaster-General was first appointed for New South Wales in 1809), but a single national postal service wasn’t established until Australia itself was established in 1901 and the colonial postal services were merged, and even then it was a government department until 1975, and wasn’t corporatised until 1989 and remains government-owned to this day.
> [...] MyFireWatch shows exactly where those active fires are.
I didn’t link to MyFireWatch precisely because it is showing ‘hotspots’ from the past 72 hours, which is not necessarily the same thing as mapping actual reported fires, hence the confusion of some of the maps talked about in the article. The data on MyFireWatch on areas which have burned is also very inaccurate for some states (Tasmania and Victoria at least).
MyFireWatch explicitly says not to use their map in an emergency[0], because the ‘latest’ hotspot data can be up to four hours old, can be up to 2km out of place (5km in extremes), and may not show fires obscured from or otherwise undetectable from the satellite.
As the BBC article suggests, generally the most accurate maps of where recent fires are and how much they’ve burnt are the state government fire or emergency services websites. Unfortunately they are state-by-state (which isn’t usually a problem, but does mean there’s not a good whole-of-Australia map), and some of them show all emergencies, not just fires.
The diaeresis and umlaut are literally exactly the same Unicode character and the symbol or diacritic itself can be called either. The difference is what it does to the vowel — it’s a diaeresis if it indicates a repeated vowel, and an umlaut if it modifies the vowel sound.
The New Yorker is kind of well known for being virtually the only significant English publication which uses a diaeresis (the ¨) where almost everyone else uses a hyphen or just two repeated letters [0].
That’s weird — something else must be influencing the translations.
I’m aware that “condescendiente” doesn’t mean “condescending”, but I’m taking it as evidence that Google Translate interpreted “patronize” with the “to condescend” sense rather than the “to sponsor or support” sense, meaning that word-sense disambiguation works better in those instances.
Yep, I’d put money on Google Translate interpreting the English wrong in the first place. I’ve just tried a bunch of variations on “don’t patronise me.” and these are the results:
"Don't patronise me.” -> "No me patrocines.”
“Don’t patronize me.” -> "No me patrocines.”
"Don't patronise me!” -> "¡No me patrocines!”
“Don’t patronize me!” -> "¡No me patrocines!”
"Do not patronise me.” -> "No me patrocines.”
"Do not patronize me.” -> "No seas condescendiente conmigo.”
“Do not patronise me!” -> "¡No me patrocines!”
"Do not patronize me!” -> "No seas condescendiente conmigo.”
Word-sense disambiguation seems to work if you write “do not” instead of “don’t” and use ‘-ize' spelling, it fails otherwise.
> Translate "patronize" and it will give you "patrocinar", which means "to sponsor”.
That translation is pretty accurate for at least one of the senses of patronise, though. Word-sense disambiguation is what’s failing Google Translate in that case.
Well, as the linked post says in the first paragraph, almost 90% of the 554 new characters aren’t emoji, and include four new scripts (used by several different languages) and additions for several other scripts. Emoji are only mentioned once in the first half of the article, and unless you consider accessibility-related emoji to be only for a “fringe diversity group”, I’m not sure how the newly added emoji [0] could be particularly controversial?