4 ms·
A related issue: Some random old, normal symbols are, for some reason, nowadays displayed by many fonts as emojis, i.e. as colored pictures. For example, the "l
by cubefox 5y ago
A related issue: Some random old, normal symbols are, for some reason, nowadays displayed by many fonts as emojis, i.e. as colored pictures. For example, the "left right arrow" symbol, commonly used in formal logic for "if and only if", now often appears white with a blue background: ↔. While others have been left untouched, like "left arrow": →. This is so annoying if you actually need that symbol in a logical context! Basically, they have made the symbol unusable in many fonts. They should have added a special emoji symbol if they wanted picture arrows...
- sebmellen 5y agoProof of problem attached… https://ibb.co/G30YR3R https://ibb.co/G30YR3R
- saagarjha 5y agoMore amusingly is that this is platform dependent. For example, on macOS ↩ U+21A9 LEFTWARDS ARROW WITH HOOK shows up as monochrome but on iOS it is rendered with colors.
- mmis1000 5y agoThat is more a problem on mac. Windows still defaults these to white and black version, unless you prepend variant selector to optin into the emoji version. Some softwares do intentionally ignore the default and turn they into emoji (discord for example), but that is a software thing. And also, white and black rendering can be forced with variant selector if you absolutely don't want them to be emoji. (again, if software don't mess them up intentionally) See also: https://en.m.wikipedia.org/wiki/Variation_Selectors_(Unicode_block) https://en.m.wikipedia.org/wiki/Variation_Selectors_(Unicode... BTW, windows used to have a bug that its emoji keyboard outputs arrow without variant selector, so it is not even a emoji when displays on windows, but it is now fixed. Proper selector (0xfe0f) have been pretended to the character.
- cubefox 5y agoOn Android the problem also occurs. The variation selector for text (︎) does not work for me either: Neither after symbol: ↔ Nor before symbol: ↔
- mgdlbp 5y agoHN strips the variation selectors—there aren't any in your comment (also, they go after, like combining characters). What do you see here? https://qaz.wtf/u/show.cgi?show=15%3A%E2%86%94%EF%B8%8E+16%3A%E2%86%94%EF%B8%8F+none%3A%E2%86%94 https://qaz.wtf/u/show.cgi?show=15%3A%E2%86%94%EF%B8%8E+16%3... Edit: I think you're stuck with the emoji arrow for that font: neither U+2194 ↔ LEFT RIGHT ARROW nor U+2B0C ⬌ LEFT RIGHT BLACK ARROW have any defined variation sequences. ⇔ and ⟺ are probably text-style, but you can't change existing content. Hmm… U+2192 → RIGHTWARDS ARROW doesn't vary either, but U+27A1 BLACK RIGHTWARDS ARROW does: https://qaz.wtf/u/show.cgi?show=15%3A%E2%86%92%EF%B8%8E+16%3A%E2%86%92%EF%B8%8F+none%3A%E2%86%92+|+15%3A%E2%9E%A1%EF%B8%8E+16%3A%E2%9E%A1%EF%B8%8F+none%3A+%E2%9E%A1 https://qaz.wtf/u/show.cgi?show=15%3A%E2%86%92%EF%B8%8E+16%3... …and as the only one of the four in the Dingbats block, is stripped by HN.
- cubefox 5y ago:(
- ectopod 5y agoThis isn't entirely random. When Unicode started including colourful emoji rather than just monochrome glyphs they added an attribute to each character to say whether it should be rendered in colour by default. And they retrospectively gave a bunch of existing symbols the colourful attribute. As you noted, this broke a bunch of existing use cases. It is infuriating.