4 ms·
Does anyone know the background behind: > U+262B FARSI SYMBOL > This symbol is so named because as symbol of Iran it cannot be encoded in ISO standards. It w
by gfaure 6y ago
Does anyone know the background behind:
> U+262B FARSI SYMBOL
> This symbol is so named because as symbol of Iran it cannot be encoded in ISO standards.
It would seem strange that ISO standards cannot refer to countries, so I'm guessing this is something specific to Iran?
- duskwuff 6y agoISO standards refer to countries all the time -- ISO 3166 is literally all about countries, for instance. I suspect this is actually shorthand for "ISO wanted to avoid referring to countries in Unicode character names". But that ship has clearly sailed nowadays with characters like U+1F5FE ("SILHOUETTE OF JAPAN").
- _vbdg 6y ago> SILHOUETTE OF JAPAN This may sound pedantic, but Japan the island or Japan the nation? It seems to refer to the island(s). On the other hand, the "farsi symbol" is of a particular nation rather than a given set of boundaries. Nations can be renamed, but the island of Japan refers to the chunk of earth. Add to that that nations get redrawn every so often in the middle east and I can understand the position.
- dmurray 6y agoJapan is not an island. Having a distinct symbol for the 4 large islands comprising most of Japan is definitely a political statement, if not an especially controversial one.
- andyjohnson0 6y agoA quick search brought me to [1] which says: <quote> As noted by Roozbeh Pournader: Neither Farsi, nor a symbol. In real life, it is the official emblem of the goverment of the Islamic Republic of Iran. Technically that would make it a logo and thus not a suitable candidate for encoding. But Roozbeh also noted: Exactly. The funny fact is that it has been in Unicode since 1.0... </quote> How reliable this is I don't know, but it sounds plausible. [1] http://archives.miloush.net/michkap/archive/2005/01/29/363208.html http://archives.miloush.net/michkap/archive/2005/01/29/36320...
- tialaramex 6y agoIt's interesting, I'd guessed it was a compatibility choice but there doesn't seem to be any evidence for that. Aside: Microsoft sucks for having purged blogs like that one. The archive you're looking at captures most of what was once Michael Kaplan's blog at Microsoft. Kaplan was terminated by Microsoft and then died, and his blog was one of a large number of valuable blogs with insights into Windows technologies that at some point were "tidied away" because they didn't fit whatever nonsense brand vision somebody had that week.
- mark-r 6y agoI really hate the way Microsoft rearranges their web pages seemingly on a whim. You can't rely on a link to them being useful for any significant period of time, and as you note useful information is lost on a frequent basis.
- saagarjha 6y agoIt’s not just Microsoft. Apple regularly deprecates and moves around or deleted old documentation, too.
- tialaramex 6y agoWhere applicable: Look for URLs in aka.ms - this looks superficially like a link shortener but (whether by corporate policy or just people inside Microsoft agree with us) they are maintained so that when the pages are all shuffled around the aka.ms links still get where you were going. https://aka.ms/RootCert https://aka.ms/RootCert will always be Microsoft's Root Trust programme documentation (how a Certificate Authority like Let's Encrypt gets themselves listed as trusted in Windows) even when Microsoft decides that page should now be in the form of a GIF anim or a 3D bullet hell game.