> it's no longer a Japanese word, and doesn't have to follow Japanese rules
No word ever has to follow any rules. Nonetheless it's pretty typical for loan words to keep rules like this from the source language, at least until different usage becomes widespread.
> Nonetheless it's pretty typical for loan words to keep rules like this from the source language
I wouldn't even know of the japanese rules to "keep" when pluralizing "emoji". Apart from that, as an city-dwelling Indian, quite a lot of our language borrows words from English and Hindi when we are not speaking either of these languages. The rules are always that of the target language, rather than the source language.
There's a decent history in English of "borrow the pluralisation rules of the source language". Many English dictionaries accept cherubim as a plural of cherub, seraphim as a plural of seraph, aquaria as a plural of aquarium, criteria as a plural of criterion, phenomena as a plural of phenomenon, referenda as a plural of referendum, fora as a plural of forum, etc.
Now, maybe this approach only applies to languages which English-speakers have traditionally considered as culturally prestigious or authoritative. Arguably that's true of Latin, Greek and Hebrew, traditionally not so for Japanese.
> These fonts are AppleColorEmoji (OS X), Segoe UI Symbol/Emoji (Windows), NotoColorEmoji (Android) and I don’t know what Linux does, but it’s probably black and white and who cares, I hear you can run bash on Windows now.
Statements like these are precisely the reason why I think getting Linux/Bash support on Windows is a bad thing.
Installing the noto-fonts-emoji package on Arch and viewing the page on Firefox, I can see the color emoji, like the popcorns before the "How did we get so lucky?" header.
I just tested the two Emoji displaying Chrome extensions on Linux and compared the output with Mobile Safari.
Chromoji [1] got all of them right, including the special Canadian flag emoji. Emojify got some of them right, but wrongly shows the flag as a "C" and "A" character and misses a few others.
OK. Stop right there. An emoji is a glyph, it need not be colored. The funny part, is that on my system and my fonts, all the examples (not provided as PNGs) are plain black-and-white renderings with the Symbola font. Even on Chrome on Linux, I don't even see the Canadian flag example she shows.
Really, most of this seems solid but it continues a rather annoying trend of assuming that Apple's font are the emoji. At least she recognizes that other fonts exist, but carries on this assumption...
More like SoftBank and NTT DoCoMo's way of enforcing their wishes on everyone else. Emoji started off as being proprietary to Japanese cellphone carriers, and got picked up by Apple when they realized they could make a killing by smoothly transitioning Japanese users to their platform.
> The funny part, is that on my system and my fonts, all the examples (not provided as PNGs) are plain black-and-white renderings with the Symbola font. Even on Chrome on Linux, I don't even see the Canadian flag example she shows.
Yeah, same here. Is there any way to fix this on chrome/firefox without changing my operating system? Because an OS requirement for a browser to render fonts properly is completely ridiculous.
hint: if you write an article about something that is broken and constantly moving by the hour, do not use that thing to document your article.
if she didn't use utf but images (to talk about the rendering) that article would have been something in 4 days, when it will be irrelevant because fonts and browsers will already have changed.
Also, people on the several platforms she dismissed as nobody-cares (android pre 5, linux, windows pre-7, etc) would have had a clue about the subject.
This seems a bit harsh. From the article, "I’m going to keep talking about the Apple font, because that’s the code path I worked on in Chrome..." Although this is toward the end of the article, it does give a good reason for why the author is only focusing on a rather small domain: she worked on this specific domain (Chrome, Apple, emoji). In case it wasn't immediately obvious, she doesn't actually mention any browser (or rendering engine) other than Chrome (Blink). Perhaps you were looking for a more complete essay on all things emoji, but it looks more like the author just wanted to write about some stuff she had worked on that she thought was interesting.
No one ever complains about the Egyptian hieroglyphs, or Linear A, or alchemical symbols, or any of the actual useless cruft in Unicode... just emoji.
Why? Is it the poo emoji? Do people hate emoji because they're popular? I don't understand. The utility of including emoji in Unicode is more evident than with a lot of other character sets. It shouldn't even be controversial.
We're using emojis as icons within an internal app now, and it works fantastically. I was kinda against emojis at first but having seen the use cases, they seem to be working out well.
54 comments
[ 2.6 ms ] story [ 169 ms ] threadI particularly enjoyed the roll-over effect on the links.
In the long run, I would have preferred Gretchen make fetch happen rather than Regina make this turn of phrase happen.
"DVD" has four syllables in Japanese. Stuff like that just happens with loanwords sometimes.
The previous poster probably meant that the Japanese pronunciation sounds like what in English would be considered four syllables.
No word ever has to follow any rules. Nonetheless it's pretty typical for loan words to keep rules like this from the source language, at least until different usage becomes widespread.
I wouldn't even know of the japanese rules to "keep" when pluralizing "emoji". Apart from that, as an city-dwelling Indian, quite a lot of our language borrows words from English and Hindi when we are not speaking either of these languages. The rules are always that of the target language, rather than the source language.
Now, maybe this approach only applies to languages which English-speakers have traditionally considered as culturally prestigious or authoritative. Arguably that's true of Latin, Greek and Hebrew, traditionally not so for Japanese.
And from OPs article:
> These fonts are AppleColorEmoji (OS X), Segoe UI Symbol/Emoji (Windows), NotoColorEmoji (Android) and I don’t know what Linux does, but it’s probably black and white and who cares, I hear you can run bash on Windows now.
Statements like these are precisely the reason why I think getting Linux/Bash support on Windows is a bad thing.
Chromoji [1] got all of them right, including the special Canadian flag emoji. Emojify got some of them right, but wrongly shows the flag as a "C" and "A" character and misses a few others.
[1] https://chrome.google.com/webstore/detail/chromoji-emojis-fo...
OK. Stop right there. An emoji is a glyph, it need not be colored. The funny part, is that on my system and my fonts, all the examples (not provided as PNGs) are plain black-and-white renderings with the Symbola font. Even on Chrome on Linux, I don't even see the Canadian flag example she shows.
Really, most of this seems solid but it continues a rather annoying trend of assuming that Apple's font are the emoji. At least she recognizes that other fonts exist, but carries on this assumption...
they are using their monopoly to push the utf groups, just like microsoft did with w3c when using IE6 monopoly. at least emoji cause less damage.
Sure, that's why we refer to them with a Japanese word.
Yeah, same here. Is there any way to fix this on chrome/firefox without changing my operating system? Because an OS requirement for a browser to render fonts properly is completely ridiculous.
if she didn't use utf but images (to talk about the rendering) that article would have been something in 4 days, when it will be irrelevant because fonts and browsers will already have changed.
Also, people on the several platforms she dismissed as nobody-cares (android pre 5, linux, windows pre-7, etc) would have had a clue about the subject.
for anyone outside the san francisco bubble (ie not using Chrome on a last model mac) this article only shows mojibake.
if you want to talk about broken rendering, always take screen shot.
I have now looked it up, and am including the definition for the convenience of anyone who also didn't know it:
It apparently stands for " For fscks sake" except with the s swapped for another letter.
Why? Is it the poo emoji? Do people hate emoji because they're popular? I don't understand. The utility of including emoji in Unicode is more evident than with a lot of other character sets. It shouldn't even be controversial.