{"id":4813,"date":"2021-11-02T13:17:48","date_gmt":"2021-11-02T18:17:48","guid":{"rendered":"https:\/\/neosmart.net\/blog\/?p=4813"},"modified":"2021-11-02T13:17:48","modified_gmt":"2021-11-02T18:17:48","slug":"microsoft-bids-adieu-to-windows-phone-in-new-emoji","status":"publish","type":"post","link":"https:\/\/neosmart.net\/blog\/microsoft-bids-adieu-to-windows-phone-in-new-emoji\/","title":{"rendered":"Microsoft bids adieu to Windows Phone in new emoji"},"content":{"rendered":"

\"\"Windows 11 is here and it comes with a new version of\u00a0Segoe UI Emoji<\/strong>, the font that’s used across the OS to render various emoji from Unicode codepoint sequences to the emoji you see on screen (developers: use Unicode.NET<\/a>\u00a0for your emoji needs!)<\/small>. With it, a number of emoji icons have been upgraded to a new look: some to mirror the connotations and semantics of other emoji fonts, others to be less disparaging. But there’s a less welcome surprise too, for those four… maybe five? of us that still remember the ill-fated Windows Phone fondly.<\/p>\n

<\/p>\n

The “Mobile Phone” emoji, perhaps better known to Unicode junkies as U+1F4F1, as depicted in Windows 10 in the default Segoe UI Emoji (see above) was a throwback to Microsoft’s short-lived Windows Phone and its tile-centric UI – often found in blue. Depending on the relative importance of a widget\/tile, a user could change its size and have it take up anywhere from a full row to a quarter of one square in a row (this lived on in some ways with the Windows 10 start menu… where it doesn’t work as well). You can see it in this picture below:1<\/a><\/sup><\/p>\n

\"\"<\/a><\/p>\n

Using what was clearly a Windows Phone was a somewhat cheeky way for someone at Microsoft to give that phone and its UI one last hurrah, in a “we’ll never forget you” kind of way… except, of course, it seems that Microsoft\u00a0did<\/em> forget all about the Windows Phone in the latest update, for this is what we now see:<\/p>\n\n\n\n\n\n\n\n\n
Emoji<\/th>\nOld (Windows 10)<\/th>\nNew (Windows 11)<\/th>\n<\/tr>\n<\/thead>\n
Mobile Phone (U+1F4F1)<\/td>\n<\/td>\n<\/td>\n<\/tr>\n
Mobile Phone with Arrow (U+1F4F2)<\/td>\n\"\"<\/td>\n\"\"<\/td>\n<\/tr>\n
Vibration Mode (U+1F4F3)<\/td>\n\"\"<\/td>\n\"\"<\/td>\n<\/tr>\n
Mobile Phone, Off (U+1F4F4)<\/td>\n\"\"<\/td>\n\"\"<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Apart from the actual phone being depicted (which is now a generic clonephone), the design hasn’t changed much. In the case of U+1F4F2, the red arrow better matches the (bulky) aesthetics of the rest of the emoji, but the emoji still don’t take up a constant width so as to line up nicely. Microsoft’s next major emoji update, dubbed “Fluent Emoji,” is supposed to be coming soon<\/a> – but if early preview is remotely accurate, it looks like the new emoji belong on the set of Wallace and Gromit<\/em> or some other clay animation kids TV show.. Here’s to hoping the preview was just a prank!<\/p>\n

\"\"<\/a><\/p>\n

  1. Photo credit: The Verge<\/small> ↩<\/a><\/p><\/li><\/ol>","protected":false},"excerpt":{"rendered":"

    Windows 11 is here and it comes with a new version of\u00a0Segoe UI Emoji, the font that’s used across the OS to render various emoji from Unicode codepoint sequences to the emoji you see on screen (developers: use Unicode.NET\u00a0for your … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":505,"featured_media":4816,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[957,1014,22,1013,1015],"class_list":["post-4813","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software","tag-emoji","tag-fluent","tag-microsoft","tag-segoe-ui-emoji","tag-windows-phone"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/neosmart.net\/blog\/wp-content\/uploads\/2021\/11\/Windows-Phone.jpg","jetpack_shortlink":"https:\/\/wp.me\/p4xDa-1fD","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/4813","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/users\/505"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/comments?post=4813"}],"version-history":[{"count":7,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/4813\/revisions"}],"predecessor-version":[{"id":4830,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/posts\/4813\/revisions\/4830"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media\/4816"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/media?parent=4813"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/categories?post=4813"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/neosmart.net\/blog\/wp-json\/wp\/v2\/tags?post=4813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}