U+237C ⍼ Right Angle with Downwards Zigzag Arrow
ionathan.ch
ionathan.ch
(A) It's in the math section, (B) it's with angles, (C) the thunderbolt ↯ is commonly used for "not" or more specifically for dis-proof in this area and
(D) at least by my 30 s internet search on a mobile phone I couldn't find any other "no-angle" or "no-right-angle" symbol.
Someone could argue that usually you use a simple strike through as like as in ≠ (unequal), ∉ (not-element-of) or ∅ (empty set) but I would say it was chosen to avoid confusion in this case. The angle itself (without the "no/not") consists of only to orthogonal lines so it would be kinda complicated to "strike it though" in any direction without ambiguity that would resemble a triangle, a fork or whatnot.
■
Any examples?
But maybe "commonly used" was maybe the wrong term. More appropriately: "sometimes" or "by some".
http://mirrors.dotsrc.org/ctan/info/symbols/comprehensive/sy...
There are lots of examples of the lightning bolt in there. In fact, under ulsy Contradiction symbols, there are four variants.
I also noticed the exact symbol being discussed is listed under "Angles".
Yes, we indeed used and afaict still use the thunderbolt for contradiction in my German university.
However "perpendicular" and "bottom/falsum" are two different Unicode codepoints with very similar glyphs.
This symbol doesn't have that box, so I don't think it's a right angle.
[0] https://en.wikipedia.org/wiki/Right_angle#/media/File:Right_...
Edit: This merely adds to the confusion, since the name of the glyph contains the words "right angle."
¯\_(ツ)_/¯
> In Unicode, the symbol for a right angle is U+221F ∟ RIGHT ANGLE (HTML ∟ · ∟). It should not be confused with the similarly shaped symbol U+231E ⌞ BOTTOM LEFT CORNER (HTML ⌞ · ⌞, ⌞). Related symbols are U+22BE ⊾ RIGHT ANGLE WITH ARC (HTML ⊾ · ⊾), U+299C ⦜ RIGHT ANGLE VARIANT WITH SQUARE (HTML ⦜ · ⦜), and U+299D ⦝ MEASURED RIGHT ANGLE WITH DOT (HTML ⦝ · ⦝).[5]
> In diagrams, the fact that an angle is a right angle is usually expressed by adding a small right angle that forms a square with the angle in the diagram, as seen in the diagram of a right triangle (in British English, a right-angled triangle) to the right. The symbol for a measured angle, an arc, with a dot, is used in some European countries, including German-speaking countries and Poland, as an alternative symbol for a right angle.[6]
The article notes that sans a given meaning the glyph was given a “descriptive name”.
So you’re not wrong? :-P
I don't think it's that common. At least, I don't recall seeing it ever. Maybe it's used in non-English mathematics?
Wikipedia mentions it's also used in electrolysis so maybe this new one is related to that somehow?
So for "not a right angle" I'd have expected a "right angle" symbol with a slash through it.
And some commenters said they used it to mark proof by contradiction, but why is there a need to mark it when you are showing it via proof? A canonical example of proof by contradiction is proving sqrt(2) is not rational. Never have I seen it marked with that symbol. Where would you even mark it? At the beginning with the assumption? Or at the end like QED?
"By way of contradiction suppose P, then ..., thus ~P ↯. Therefore ..."
[0] https://en.wikipedia.org/wiki/Contradiction#Symbolic_represe...
https://emojipedia.org/person-in-suit-levitating/
(Edit: Apparently HN automatically removes emoji.)
https://en.wikipedia.org/wiki/Miscellaneous_Technical
Aside from the table describing each symbol, if you scroll to the bottom of the page, it links out to full articles related to each. For a full list see...
How did it we end up with so many characters of unknown origin?
I had no idea what it meant or was used for, thus assigned it a “descriptive name” when collating the symbols for the STIX project. (I still have no idea, nor can supply an example of the symbol in use.) […] it is the case that ISO 9573-13 existed long before either AFII or the STIX project were formed. […] I once asked Charles Goldfarb what the source of these entities was, but remember that he didn’t have a definitive answer.
I worked at a large media company that had lots of differing icon sets in play across different media.
These icons were in SVG and they had been optimized pretty intensely. In some cases due to a bug in one of the optimizing tools some types of bezier curves got weird, so instead of say the round headed person with their hand held up to say stop it was the star headed monstrosity pointing to doom from the heavens. Because of how the icons were used and not used these optimized errors were actually sitting around so long that nobody had examples of the original icons although one could guess because in some cases we had similar ones in other projects that had not been optimized.
So maybe a similar thing would be the source of these weird alien entities.
No it did not. Klingon was originally proposed in 1997 and rejected in 2001. A second proposal was made in 2016 with more optimistic noises. But AFAIK it has yet to be accepted.
It is also, like Tengwar and Cirth (which AFAIK remain unincluded even though they are on the BMP roadmap), held back on IP grounds. To my knowledge, the IP issues remain fully unresolved.
Klingon is included in the ConScript registry, but that is unrelated to unicode itself, it performs ad-hoc and non-standard allocations in private use areas.
That sounds like a useful reaction/ response these days.
Could someone please feed that to DALL-E?
What monster hath we unleashed?
Could be any random kid who found out about this and wanted the cool symbol they made up registered.
(Might need to add this: https://en.wikipedia.org/wiki/The_Crying_of_Lot_49)
Due to this thorough investigation, the committee was able to pare down the number of kanji for which the source cannot be confidently explained to twelve, shown on the adjacent table. Of these, it is conjectured that several glyphs came about due to copying errors. In particular, 妛 was probably created when printers tried to create 𡚴 by cutting and pasting 山 and 女 together. A shadow from that process was misinterpreted as a line, resulting in 妛 (a picture of this can be found in the Jōyō kanji jiten).
Here I'll date myself: I remember this as "diode with a gate". Back when we did circuit diagrams with stencils, you had the diode stencil which looks like a triangle with a line on top, and then with the electrical stencils you had "decorations".
The intention was to put down the original symbol on the paper, move the decorations stencil over top of it and then add the required decorations. It's why diode symbols look like this: https://imgur.com/a/0tSLV7O (notice "step recovery diode").
The "lightning bolt" isn't a lightning bolt, it's a hint that this diode is going to have a very sharp "snap off" in the waveform. See: https://www.electronics-notes.com/articles/electronic_compon...
OK so why do we have a seperate decorator for a diode? Can't we just have a pocket full of stencils for diodes? Space was at a premium back then. It goes back to daisy wheels and typeballs: https://en.wikipedia.org/wiki/Printer_(computing)#Impact_pri... You would have one position for "diode" and one position for "decorator" and the printer would know when it got one ASCII char it would print the diode, then send whatever the thin space is to advance the print carriage a small step, then print the decorator.
Someone should be able to find a daisy wheel or typeball dedicated to circuits and bear this out.
You can't view an image without JavaScript. Once you enable it you get "f*ck your privacy" popups, and ads if you don't have a blocker. On mobile I can no longer view anything on imgur at all, only the top bar renders for some reason. There seems to be no way around this.
It was also recently, although after the downhill, bought by a company that specializes in buying dying social media platforms and milking them dry with questionable ethics. How questionable? Well, they got into a Darknet Diaries episode https://darknetdiaries.com/episode/93/
For a second I was thinking you meant this as the correct definition of the symbol, and was very surprised :-)
|
| \
| \
| \ /\
| \/ \
| \
| _\/
|
+———————————————
Could (more or less) fit that description and would make more sense as a symbol. Something like it even made it into Unicode (https://emojipedia.org/chart-decreasing/)It's like o7 vs 7o; if you know you know: http://i.imgur.com/ZjhHU87.jpg
It looks like a symbol that someone added for completeness but isn't particularly useful even in the field.
Some also were used as submissions for projects, long before sites like sourceforge started. Especially since plonking a bigger source dump on newsgroups wasn't exactly well received.
In The Netherlands, in the nicer neighborhoods we have something called a ‘buurtbieb’ aka a ‘neighborhood libraries’, which is a weatherproof cabinet where people can put surplus books that other people in the neighborhood can borrow.
Of course you could take all the books or use the cabinet to store candy, but why would you?
(The name is a little weird, because regular libraries are also free...)
Private libraries (mine for example) are not free, as in beer or otherwise.
People tend to call their personal library a "book collection" or the like, but it's a library, in just the same way that a Little Free Library is.
So most people who read have at least a small private library, whether they think of it in those terms or not.
Furthermore, public libraries are not necessarily free. In America they virtually are all; fees only for late returns. But this is not globally true; in some parts of the world, libraries open to the public charge a fee for checking out books, or even require a fee for entry.
It's a literal translation of "neighbourhood library", it alliterates, and it sounds cute. (Keep the "beep" part short for that).
Good luck getting a jury to enforce the trademark.
That’s like saying it would be naive and irresponsible for me to go outside without a life preserver today despite an unforeseen catastrophic global flood drowning the lands 10 years from now. It was a different world, with different expectations and frameworks.
That was a good and fun security lesson though and now I always check outside security with a mobile hotspot.
- "Man, those idiots are naive and irresponsible."
2 it s not like other people cant go to those places, thus it is kinda irresponsible
Meanwhile internet aint remote village
.
[1] A synonym for "goods" or "products". See https://www.merriam-webster.com/dictionary/wares
Anyway, by 1990, in the piracy circles I distantly associated with, it was quite common to pronounce it like "juarez". Sort of semi-ironically, like, it's obviously the wrong pronunciation, but nonetheless everyone uses that pronunciation on purpose. So, what could be more correct than "the thing everyone does"?
Of course, pronunciation only happens in meatspace (or at least it did back before MP3s and before YouTube and so on), and of course I'm talking about clusters of teenagers separated by thousands of km. We had "meetupz" or "meetz" in my city, which is how I know how "everyone" pronounced it... but it's certainly possible that in most cities/whatever there was some other pronunciation rule.
Citation needed there.
I have always assumed it came from fleamarkets where people selling pirated VHS films and knock-off Rolexes would be described as “selling their wares”. Changing the s to a z was an obvious step in 90s internet culture.
Pirate BBSes would have various "goods" (in the sense you and GP mean) available for download, including images (hint: some of them may have involve ladies), text files, and software. Sometimes there would also be sections for various art media created by users, such as .mods or ASCII art or poetry or whatever. Those various "goods" would never be all slopped together, they'd be divided into categories. And the category called "warez" would never, ever, have anything in it other than pirated software.
I agree that the s-to-z thing is just classic hacker/leet culture, though it's not internet culture, because it predates the people in question having internet access. I'm saying that the "wares" that becomes "warez" is not "wares-as-in-goods", it's "wares-as-in-softwares". It's pluralized even though "software" is a non-count noun, because then it fits with "files", "images", and so on. And yes, ultimately the "-ware" in "software" is from the sense that you and GP are talking about; I'm saying that the etymology is not directly from there, because otherwise all the other kinds of pirated stuff would also be "warez", and it never, ever, was.
I think it was explicitly luls a lot of the time. I saw "warez" spelled as "juar3z", etc, a lot.
- war-ehz
- gee-aw-cit-eez
- jif
https://ja.wikipedia.org/wiki/%E5%B9%BD%E9%9C%8A%E6%96%87%E5...
For Japanese, it requires a minimal of few thousands of characters and symbols and it still doesn't cover all the commonly used characters today.
Unfortunately even she is not aware of what the symbol is actually for.
[0] https://www.ams.org/STIX/bnbranges.html [1] https://tex.stackexchange.com/a/640596
This post is from 2015, and I'd love to know if unicode has added better support for non-English languages since then.
https://modelviewculture.com/pieces/i-can-text-you-a-pile-of...
Based on https://en.wikipedia.org/wiki/Bengali_(Unicode_block), only 3 more Bengali characters have been added since 2015.
I am not a Bengali-speaker, but I am familiar with the class of scripts to which the Bengali script belongs, abugidas. These scripts assume a vowel following every consonant. When two consonants occur one after the other in a word (a consonant cluster), this must be represented specially, because if you just wrote (consonant, consonant) it would be pronounced (consonant, inherent vowel, consonant).
The "ty" in Aditya is one such consonant cluster. The way this cluster is written is ত্য. This is represented as three code points (I think I am messing up the proper terms), one for the "t", one to "join", and one for "y".
Some people think of the special shape that the final "y" as a separate character on its own. In fact, it has it's own name (ya-phalā). I can understand why it would be confusing to see that the ya-phalā can't be typed as its own single character (" ্য"), but it really has to do with a difference in how the input is is implemented and how the person thinks about their own language.
In fact, on the unicode.org site, typing this very character is part of the FAQ for Bengali: https://unicode.org/faq/bengali.html#6
It's complicated, but the author of the piece seems to take issue with how the character set was designed by the language authorities the UTC delegated to.
The whole comment thread is an interesting read.
Tell us that story please!
I’m guessing the person who implemented it got this exact requirement wording in the Unicode definition and nothing else, didn’t make the logical connection, and just implemented it as close to literally as they could.
⍼ (U+237C) is in Unicode 3.2 (from 2002), (U+1F4C9) is from Unicode 6.0 (from 2010).
[edit]: HN ate my 1F4C9 glyph. Use your imagination :)
> I had no idea what it meant or was used for, thus assigned it a “descriptive name” when collating the symbols for the STIX project.
If I understand this correctly in the context, this person named the glyph based on what it looked like. So it wasn't the other way around.
Or a lightning bolt through a window (with only the bottom-left of the window frame being visible).
Surely the archeologists of the future won't have to wonder what some tool from our times was used for or what some symbol we currently use means… They will have Wikipedia and archive.org and whatnot!
But that fantasy is not compatible with reality where we are already unable to find out what is the purpose of some characters in Unicode.
There's no saying that there'll be a society capable of reading bits and bytes by then. Not just collapsed society -they'll hardly be interested in reading a random discussion on an orange forum for a niche group that lived 8000 years ago- but maybe even societies that are vastly technical superior to our own but cannot fathom what things meant 8 millenia back. I mean we have texts from some 600 years ago, that we can read, but cannot understand (e.g. Rohonc Codex). Eventhough our technology and knowledge is far superior to when it was written.
"Why do people in this group of wall drivers show off their wedding bands?"
Number one post is the Linking Sigil. Neat.
If you know, you know.
As for how a chaos magick symbol concocted in the 21st century ended up in a 1994 font spec, clearly discordians used the power of fnord to retcon it.
But the rest of the article is concerned with how mysterious the symbol is, and how no one knows where it came from.
A clue: anyone can register a symbol for a surprisingly small fee.
A question: why would the sigil be mentioned in an addendum but not in the article proper?
Anyway, it's pretty obvious that GP had a premonition this morning, with a pay off.
A unicode symbol? I want a symbol! How much are we talking about?
If you do, can you please tack on symbols for following external links, space bar symbol, and all the other miscellaneous internet adjacent characters I always have to reach to Fontawesome for?
As another comment mentions, once you add all these snowmen, with/without snow, male female and gender-neutral, in a few skin colour options (plus neutral)... it adds up. Plus, exponential growth once you consider family of snowmen (different number/genders/races of "parents", different number/gender/races of "children" and so on...).
And in the unlikely case that Unicode gets so many characters somehow, you can always extend it: http://ucsx.org/
Perhaps not by a significant or even measurable amount. Nonetheless, it's a great reason to start investigating a blockchain alternative to Unicode
> Will Unicode be flooded with symbols for many crypto-currencies?
> Most other crypto-currencies have learned from the difficulty that a non-Unicode symbol causes for Bitcoin, and use a symbol already in Unicode. For instance, Dogecoin uses Đ, Ethereum uses Ξ, Litecoin uses Ł, Namecoin uses ℕ, Peercoin uses Ᵽ and Primecoin uses Ψ. Some, like Ripple, use Roman capital letters (XRP), mimicking ISO 4217 currency codes.
> While it is possible another crypto-currency will have a non-Unicode symbol that is extensively used in text, this is unlikely.
I think this section was crucial for the eventual acceptance, because Unicode people do care (a lot) about long-term consequences of proposals.
The downside of this approach is size: each tag codepoint (including the end marker) requires four bytes in UTF-8, plus two for ¤, so the sequence above is 18 bytes long.
[0] https://en.wikipedia.org/wiki/Tags_(Unicode_block)#Current_u...
For national currencies, perhaps. New national currencies aren't introduced all that often, and there is a lot of pressure to support them quickly as their use is often mandatory for anyone living in that jurisdiction. For new private currencies, including crypto-currencies, we don't see quite the same eagerness—the observation that new crypto-currencies were more likely to reuse existing Unicode symbols than invent new ones was a consideration in getting the Bitcoin symbol adopted, as they didn't want to open up the floodgates to large numbers of new currency symbols. The tag-based system offers a compromise.
> and more than one currency symbols for given ISO 4217 code can exist so I don't think it would work
That is a bit of a problem, but it could be handled with the variant selector codepoints, for example ¤MOP = MOP$, ¤MOP(VS1) = 圓, and ¤MOP(VS2) = 元, if the symbols have the same meaning. To save some space the VS could replace the end codepoint. For fractional units there could be a different prefix such as ¢ for 1/100 or ₥ for 1/1000 in place of the ¤, or incorporating one of the Unicode fraction codepoints for other ratios up to ⅞ (or ⅑ or ⅒). These would be rendered verbatim in the fallback version, like ¢USD.
A good tool to see this broken down is https://unicode-x-ray.vercel.app/?t=%E2%9C%8C%F0%9F%8F%BC%F0... (edit: fixed url to use percent encoded emoji)
It's your device rendering these 2-3 byte character sets as single icons/emojis.
FWIW that's true for the skin colors (there are 5 fitzpatrick scale modifiers, U+1F3FB to U+1F3FF), but it's not true for the gender: the basic gendered characters (e.g. U+1F468 "MAN", U+1F469 "WOMAN") were part of the original set "merged" from japanese emoji so the gender-neutral equivalent (e.g. U+1F9D1 "ADULT") was added as a separate codepoints.
[0]: https://www.unicode.org/L2/L2016/16181-gender-zwj-sequences....
IPv4 ran down because everything needs an IP to be on the net and there are more humans than available addresses, and more gear than humans.
We don't need different characters per human, only to document existing languages and to account for the slow growth of modern hieroglyphs.
Note that as it is currently defined, the Unicode codespace ranges from U+0000 to U+10FFFF, with some reserved codepoints (eg to encode surrogate pairs), yielding a total number of 1,112,064 assignable code points.
I find it completely implausible that this will ever change: the current size is baked in too heavily.
• The abomination UTF-16, which is distressingly popular, cannot possibly support it. Replacing UTF-16 would be a massive upheaval in many ecosystems (e.g. JavaScript, Qt, Windows), and there’s no real prospect of most of those environments moving away from UTF-16, because it’s a massive breaking change for them by now. Rather, if the code space were running out, they’d devise something along the lines of second-level surrogate pairs. (And then we’d curse UTF-16 even more, because it’d have ruined Unicode for everyone again.)
• All code that performs Unicode validation (which isn’t as much as it should be, but is still probably a majority) would need to be upgraded. Any systems not upgraded would either mangle or more commonly fail on new characters.
• UTF-8 software would also need to be adjusted, since it’s artificially limited to the 21-bit space; and it wouldn’t be just a matter of flipping a few switches here and there to remove that limit—there will be lots of small places that bake in the the assumption that representing a scalar value requires no more than four UTF-8 code units.
Unicode encodings are separate standards that give correspondences between Unicode code points (integers) and byte sequences. If Unicode changes in a way that invalidates an encoding, that just calls for a new encoding.
While UTF8 was originally defined as able to encode 31 bits, because of the limitations of UTF-16 RFC 3629 explicitly restricted the unicode code-space to 21 bits (or about 1.1 million codepoints).
Unicode NFTs here we come
There are not separate code points for all combinations of genders and skin colors; the characters are made as combinations.
No. There are currently 144697 codepoints allocated, out of a possible 1.1 millions. And most updates allocate a few hundreds. The large allocations (in the thousands at a time) overwhelmingly concern large additions of CJK unified ideographs (see: 13.0 with 4969 out of 5930 new codepoints, 10.0 with 7494 / 8518, 8.0 with 5771/7716).
There have been large additions of historical scripts (9.0 added the entire Tangut script, 7.0 added 23 different scripts) but those occurrences have slowed down a lot.
So in a way, Unicode is already long past the time where you invent NATs and other hacks to buy you time with the scarcity problem.
It really, really doesn't.
According to UTS #51, as of unicode 14 (and its ~140000 allocated codepoints) there are under 3500 codepoints classified as emoji.
And do keep in mind that #, or ®, are classified as emoji.
And incidentally, U+2654 "white chess king" (♔) was in unicode 1.0. The moral panic around emoji is really tiring, it's absolute, utter nonsense, every single time.
Amongst other things, hitting the limit of 16 bits meant the introduction of:
- The concept of "planes"
- UTF-16 combining characters
- UTF-32
- The newfound desire to encode emoji using combining characters, which means many apparently simple emoji are actually hacked together out of a mini programming language (e.g. black man = man emoji + skin tone modifier). Same thing for flags, which are actually two English letters mapped into a different part of the code space and then combined e.g. the British flag is G+B.
It's one reason why emoji broke so much software. It used to be that before emoji nobody cared about characters beyond the basic multilingual plane and ignored them. Then emoji came along and broke everything that assumed a UTF-16 code point == a character.
> To skip certain steps in order to do something as easily or cheaply as possible, usually to the detriment of the finished product or end result.
"oikolukumerkit" found an image with more than just the DIN referenced marks, but not much more.
There is the U+1F517 link symbol but I'm not sure that's communicating the same thing.
Wikipedia uses it.
edit: the right angle portion of it looks like the symbol for 3 wire 2 phase electricity used here - https://www.conceptdraw.com/How-To-Guide/qualifying-symbols ..Yes, it is just a right angle. but I could see the electricity symbol being overlaid to indicate that it was an electrical symbol.
https://stackoverflow.com/questions/6638471/why-does-the-uni...
To quote a reply from the above StackOverflow thread: "So, they added a snowman with snow AND a snowman without snow , so that the weather forecaster of this world can avoid the dull snowflake , but we will never get our missing superscript q‽"
And, BTW, what do you mean by "all letters"? Should Unicode contain sub/superscript variants of Hangul or Devanagari or letters from hundreds other non-latin-alphabae languages? So, Unicode must be approximately tripled, bar hieroglyphic part (and why hieroglyphics should not be sub/superscripted?)?
Nope, you'd use markers similar to U+200E (LEFT-TO-RIGHT MARK) and U+200F (RIGHT-TO-LEFT MARK) that already exist to indicate text direction (which is also a typesetting property).
Why? They could have left this for a higher layer to handle.
In my opinion, yes. If it can't, it's not fit for purpose, no matter what is or is not an intrinsic property of some characters...
Unicode specifically states that it doesn't define the semantics of characters. That would seriously interfere with its purpose of defining characters.
There are some notable exceptions, and they are acknowledged to be mistakes.
The Unicode Standard explicitly says otherwise:
> Characters have well-defined semantics. These semantics are defined by explicitly assigned character properties, rather than implied through the character name or the position of a character in the code tables (see Section 3.5, Properties). [1]
> The Unicode Standard associates a rich set of semantics with characters and, in some instances, with code points. The support of character semantics is required for conformance; see Section 3.2, Conformance Requirements. [2]
To be fair, it refers to "character" semantics which is more or less abstracted by character properties. It is not like that, for example, △ U+25B2 WHITE UP-POINTING TRIANGLE UNICODE CHARACTER can only ever be used for denoting triangles. But it has defined semantics in the way that the character has properties expected for such symbols.
[1] https://www.unicode.org/versions/Unicode14.0.0/ch02.pdf#page...
[2] https://www.unicode.org/versions/Unicode14.0.0/ch04.pdf#page...
But to be honest I'm not sure what the parent comment wants to see added because at the moment having all the letters from A-Z, numbers from 0-9, and plus minus and equals signs as both subscript and superscript seems to be enough.
Also, I've seen a lot of different symbols as subscripts in mathematical and physical articles, like squares, triangles, arrows, etc.
Sure: As I mentioned in another comment, I'd add markers to enable arbitrary super and subscripting.
However, the question I responded to was asking what specifically people were missing in practice, and the examples I gave are things I personally would have used if they had been available.
There are a ton of places that don't support superscript markup.
Well, that's really a better solution. Or a unicode character that allows you to set a pixel on a 256x256 grid and one to compose them. Strike that. Better not give anyone bad ideas.
If emojis weren't allocated out of compatibility concern, this would be exactly my opinion from the day 1. To be honest I'm not still happy with the current emoji assignments and semantics. Not even Unicode people are satisfied either, there are numerous proposals for replacing emoji with something else (example keyword: QID emoji).
> RTL markers shouldn't be added because you should use dedicated text styling for that.
> There are a ton of places that don't support superscript markup.
Unlike most text attributes, bidirectionality is an intrinsic property of abstract characters and thus absolutely within the Unicode's scope. Ideally you can't and shouldn't make some LTR character to behave like RTL characters or vice versa. Bidi control characters only exist to correct automatic rendering, and can be presented out of band (the Bidi specification is explicitly designed for this use case in mind [1]).
[1] https://www.unicode.org/reports/tr9/#Markup_And_Formatting
That would triple the size of Unicode.
The things people write about...
And yeah, actually a downward zig zag on a x/y plot glyph would be useful to have.
Like "chart with downwards trend" added to Unicode 6.0 in 2010, 25 years after "right angle with downward zig zag" was proposed and included.
Or, maybe not and we'll continue to lose formatting every time we copy and paste and be forced to use plain text for the rest of our lives. Also, we can color our emojis now, but that WARNING text can't be in red. Because colors don't matter?
Which ever person decided basic formatting shouldn't be in the spec was wrong and we lose important details every day because of it.
> When writing in languages such as Danish and Norwegian, where the empty set character may be confused with the alphabetic letter Ø (as when using the symbol in linguistics), the Unicode character U+29B0 REVERSED EMPTY SET ⦰ may be used instead
≤ U+2264 LESS-THAN OR EQUAL TO
⋜ U+22DC EQUAL TO OR LESS-THAN
≥ U+2265 GREATER-THAN OR EQUAL TO
⋝ U+22DD EQUAL TO OR GREATER-THAN
or even ⋚ U+22DA LESS-THAN EQUAL TO OR GREATER-THAN
⋛ U+22DB GREATER-THAN EQUAL TO OR LESS-THAN> ⋛ U+22DB GREATER-THAN EQUAL TO OR LESS-THAN
These are very interesting. What would be the use case for these?
There are lots of similar symbols: ≶≷≸≹⋚⋛⪋⪌⪏⪐⪑⪒⪓⪔
> If the function f is differentiable and concave, then f′(x1)⋚f′(x2) as x1⋛x2. That is f′(x1) and f′(x2) have the opposite relation as x1 and x2.
"Related terms
⋛ (synonymous when used on its own, but antonymous when used jointly)"Unlike other waves like sound waves, EM has polarization component.
In wireless communication, for example, polarization can be used as another component for diversity to increase the performance of the communication channel.
https://tex.stackexchange.com/questions/640588/what-is-%E2%8...
Could this be The American Mathematical Society?
> It appeared in the entity set ISOAMSA, which, regardless of the name, had no connection with the American Mathematical Society.
Now we have an XKCD for this.
Translation: Nothing came up on a Google search, and going to the library and looking in a book is hard.
I see this more and more often these days. Bloggers claiming that there is no known origin for something, or inventing their own histories based on nothing more than internet searches.
The internet is vast, but 99.9% of the world's history and information is not online for free.