SoylentNews is people
SoylentNews
You can now tweet a 🍕 emoji to Domino's in order to initiate a pizza transaction.
Emoji use differs by country. "Canadians lead the charge in their use of money, violence, sports-related, raunchy, and even the poop emoji," says SwiftKey's chief marketing officer, Joe Braidwood.
Americans are second behind Canada in their love of violent emojis, such as guns.
But one thing Americans also really, really love is pizza.
"Pizza was one of the most frequently used [emojis] in the U.S., as well as the chicken drumstick ... and I think it shows you that, versus other nations, you guys have particular food habits," Braidwood says.
Emoji In the Unicode standard at Wikipedia.
Draft Emoji Data at the Unicode Consortium.
💩/10.
[ED NOTE: The &#####; markup for these characters are legit. Are you able to see them, or are you seeing unknown character boxes? What font are you using? -LaminatorX]
(Score: 2, Informative) by CortoMaltese on Thursday May 14 2015, @03:03PM
Just werks in Firefox 38.0 :^)
But seriously, seeing the linked page in wikipedia, some seem to work and some don't.
(Score: 2) by Marand on Thursday May 14 2015, @08:45PM
But seriously, seeing the linked page in wikipedia, some seem to work and some don't.
I checked in Firefox 31 (the ESR one in Debian) and in Chromium (40ish). Both have been fine with everything used here, but the Wikipedia page turned up some problems. Chromium had everything, but Firefox had a handful of missing ones on it. It didn't seem to be a simple case of "change your font and it works" though, because I tried switching FF to the font Chromium used and it didn't fix it.
To investigate further, I loaded the page in KDE's editor, kate (thanks KIOslaves!) and they all showed up as long as the file encoding was set to UTF-8, but when I used the same fonts in Firefox it still showed boxes. Then I set kate to use a font I know doesn't have emoji (it doesn't even have the full ASCII set) and it stilll showed the characters.
It looks like most programs are intelligently falling back to a default "has everything and the kitchen sink" font for characters that aren't defined in the current font. And by "most" I mean Qt apps. Every Qt app I tried was flawless with it, but the Gtk apps I tried (both gtk2 and gtk3) didn't do quite as well for some reason, showing blocks on the same characters that Firefox does. The exception is webkit-based html views inside Gtk apps. For example, in Geany (Gtk-based mini-IDE), if I paste a bunch of the emoji into a markdown file, the same ones show up as square blocks, just like in Firefox, but the markdown preview shows all the characters properly.
So, the problem, at least in Linux, seems to be Gtk-related, but mitigated by webkit (and blink) doing its own thing. Firefox uses XUL for UI creation, but it's still Gtk at its base, just like Chromium. That also means that some of the characters will print fine in Chromium inside a webpage, but nowhere else in the UI. For example, in Qt apps or on the wikipedia page itself, these four symbols all show properly: 🏉 🏊 🏋 🏌 . However, only the first two displayed in the URL bar or search box (ctrl-F) in chromium, just like in Firefox. What's odd is they're clearly using the same font as the Qt apps, but just not printing a handful of the characters.
Also, unfortunately, I have no idea what font is being used as the fallback on my desktop, but whatever it is, it's not installed on my laptop because everything shows as squares there.
(Score: 4, Funny) by frojack on Friday May 15 2015, @12:11AM
Took us something like 4000 years to come up with unicode fonts capable of handling every character in every language.
Upon completing that task, we immediately (in an ooooh shiny... moment) started adding a boatload of obscure pictographs.
Are ALL our corners already filled with people humming, or what? Face it, we're all from the B Ark.
No, you are mistaken. I've always had this sig.
(Score: 2) by takyon on Friday May 15 2015, @01:54AM
Everything old is new again. [unicode.org]
[SIG] 10/28/2017: Soylent Upgrade v14 [soylentnews.org]
(Score: 3, Interesting) by FatPhil on Friday May 15 2015, @08:15AM
One thing that particularly annoys me is that so many of the example renderings are completely unrelated to each other, and unrelated to the textual description of the character. Another thing is that I do not consider "Blue $X" and "Red $X" to be different characters any more than I consider "$X at size 9 pica" and "$X at size 24 pica" to be different characters. (Which is not at all.)
Thinking about it, the oooh-shiny problem even predates Win 3.0 and clipart. This is just the problem with fonts, claris draw, and party invitations made on Macs in the 80s. Every one had to have 20 fonts and swirls of baloons, hearts, bubbles, and stars.
This is why my computer has very little more than xterms running on it, and I still use w3m as a browser. You can keep the modern crap, there's more noise than signal in it.
Great minds discuss ideas; average minds discuss events; small minds discuss people; the smallest discuss themselves