> Is anyone aware why is the situation like this? Maybe because logos don't have any place in an alphabet? > it doesn't really make sense not to have them. I

> Is anyone aware why is the situation like this? Maybe because logos don't have any place in an alphabet? > it doesn't really make sense not to have them. I would claim it doesn't really make sense to have facepalm, avocado, etc. As far as I'm aware, the original set of emoji were included due to existing messages on Japanese networks using proprietary encodings. There are precisely zero existing messages containing wifi or bluetooth logos as characters; adding such things to unicode creates a problem to solve, rather than solving anything. At this point it seems like unicode is being treated as a meme database, with code points as URIs and the system font as a retrieval mechanism. This bulldozes through a number of carefully chosen separations of concern (characters/code points vs glyphs, glyphs vs fonts, fonts vs images, images vs URLs, etc.), with the only reasoning I can fathom being to fit the current implementation of the iOS on-screen keyboard.