U+237C ⍼ Is Azimuth(ionathan.ch) |
U+237C ⍼ Is Azimuth(ionathan.ch) |
A sextant can be used to obtain the relative horizontal angle between two landmarks, but it is much easier to use an azimuth ring. A sextant is designed to be used vertically. Holding and using one horizontally is difficult and time-consuming in comparison and is probably a less than a 1% use case, used only during the training of apprentices as a theoretical exercise (source: professional mariner for many years and daily user of a sextant back in the day). A comparison would be using a screwdriver to drive in a nail; you could do it given enough time, but a hammer is much easier.
I believe the explanation is much simpler: the glyph simply represents a variety of angles measured from north (the common meaning of azimuth) avoiding the use of any lettering (like “N”) or the use of a compass-like symbol which would be difficult to represent at such small scale.
Also (pedant warning for another poster) Polaris is not the brightest star, it’s around the 40th and has no practical use for navigation other than “north is roughly that way”.
The way I see it, it appears to be an arrow curling around the vertical axis, representing the turn from the angle's start to the angle's end. In that sense, the modern curvy arrow actually makes more sense than the original jagged one (which maybe was easier to typeset - or maybe just disproves my theory).
You can see one here: https://sextantbook.com/2019/01/13/a-french-hydrographic-sex...
The linked article is by W.J. Morris, and his book on sextants is in my opinion one of the standard works and much recommended.
"Haussystem Didot" in the article's referenced typesetting catalog refers to the typesetting of the Didot family's printing agency. And they used that symbol 1700 and onwards in their map navigation descriptions in these books:
https://fr.wikipedia.org/wiki/Histoire_g%C3%A9n%C3%A9rale_de...
I am gonna repeat myself, but search for the Gallica links in each of those books to find the scans. There you can see earlier usage and evidence that as I pointed out in other - downvoted comments - that this was commonly used for sextant navigation instructions.
I did not find any evidence for earlier examples in any of the very few scans I looked at, nor does a search through the Google Books scans give any indication for words that seem related to the concept.
This would be such a fantastic find! Could you point out a specific example?
-- Paraphrased from The Restaurant at the End of the Universe by Douglas Adams
Every once in a while you run into something like this and realize the standard is not just for text encoding but also a kind of archive of specialized notation from different fields.
It makes you wonder how many other symbols are sitting in the table that are still mostly unknown outside the niche communities that originally needed them.
Unicode's entire point being to make "normal software" handle those symbols ;)
For years Ł support on Python on windows for example broke sometimes when imported from poor quality Excel files haha
Maybe this is the opportunity to invent and suggest a symbol for Altitude?
Consider the Moon as viewed from NYC at time of comment [0], it is hiding below the horizon. If you were to look at my website and then at the sky you might become upset that I am reporting the shape of the moon, but obviously it can't be seen. Hence why the website reports the angle below the horizon roughly half the time it isn't visible.
Adding Azimuth and Elevation when the Moon is above the horizon would be for completionism only and not the real enterprise use-cases served by ANSI compliant renderings of the Moon.
[0] https://aleyan.com/projects/ascii-side-of-the-moon/?lat=40.7...
Ah, of course :)
A lot of old German sailor maps (e.g. from the Hamburg or Bremen maritime museum exhibitions) contain Azimutal angle descriptions. The globe on an azimutal map is projected from the North Star in the center.
This way you could more easily calculate the angles you would need to use the Sextant (which was focused on the brightest star, the North star). They also used circles (the tool) to calculate relative speeds, current drift etc with it.
I thought this was kind of common knowledge, as a lot of museums have that sorta thing for children in their exhibitions to try out.
The article quotes the Didot system, specifically, which focused on printing travel maps and is known not only in the French speaking world for its timely accuracy [1] as it was also using that very same map system.
Maybe read the article next time?
[1] https://en.wikipedia.org/wiki/Didot_family
[2] https://fr.wikipedia.org/wiki/Histoire_g%C3%A9n%C3%A9rale_de...
> From that apparent beginning, the Angzarr was swept up into the Monotype typeset catalog of arrow characters (...) It is unknown why Monotype added the character, or what purpose it was intended to serve
> In 1988, the International Organization for Standardization added the symbol to its Standard Generalized Markup Language (SGML) definition, apparently pulling it from the Monotype character set.
> In March 2000, the Angzarr symbol reached wide distribution when the Unicode Technical Committee, in collaboration with the STIX project, proposed adding it to ISO/IEC 10646, the ISO standard with which the Unicode Standard is synchronised. The Angzarr was proposed in the ISO working-group document Proposal for Encoding Additional Mathematical Symbols, although no specific purpose is listed for the symbol.
My guess is that the people proposing the addition of new maths symbols[1] weren't going to decide on inclusion or exclusion of a symbol on the basis of being familiar with it themselves or not, since that was likely true for many symbols that happened to only be used in fields of mathematics that they were not working in. Meaning they had to rely on some other kind of "authority" to infer that a symbol was used by the larger maths community. With that in mind "being part of the Monotype catalog and part of SGML" seems like a pretty sensible heuristic to go by.
Another consideration might have been that they simply wished to have complete coverage of the symbols that SGML encoded, regardless of familiarity with the symbols involved. And of course both could have been true.
Presumably its original use was in some yet-unfound paper or manual where they needed a symbol for azimuth.
Edit: Seems like the earlier attempt stopped before ever getting to the proposal stage, maybe it is worth pushing through even though some of the requirements for the unicode standards can not be met.
You may be too young to remember, but there was a time when a lot of software had their own way to encode emoji if they supported them. This sucked for interoperability - especially when using common protocols like SMS.
Some of these implementations were essentially find/replace and would turn various strings of characters commonly occurring in code into emoji. Someone reading your mail containing code on their portable device or other weird client would see parts of that code replaced by emoji. Maybe you had to format your code a certain way, inserting spaces tactically, to avoid accidentally ending up with an emoji. I'm glad we put that behind us for the most part.
Living in a world where you can just copy-paste some text containing emoji (or not) from one software into another is honestly great. Same for all these other symbols that may be embedded into text.
If a software has to come up with their own text-embeddable encodings to represent symbols (to allow for copy-paste or sharing) things often end up less than optimal.
Emojis obviously got in from Japanese character encodings, and imho the world is off better for that. Though many of the extensions of the emoji set really don't seem to get what emojis are used for. Similarly, chess and shogi pieces as well as symbols from Western playing cards go in through previous encodings, and domino tiles got accepted based on being conceptually similar. A bit questionable imho.
On the other hand the Azimuth sign seems to satifsy the "would appear in OCR scans", based on being published in font catalogues. Even if nobody has come forward with a book it appears in, I don't think they made and advertised lead type characters for fun. It has to have had some use in printed publications of some type (probably scientific, from the surrounding context)
Neither the wikipedia page for the Didot family, nor for Histoire générale des voyages shows the Angzarr symbol, I've carefully checked on all the scans on these pages. In fact, any occurrence of the symbol would pre-date the current earliest known example (1963) by 200 years, and that would be a great find. If you have an actual reference, please let us know!
"Haussystem Didot", the title of the catalog, refers to a letter setting by the printing agency Didot, which is the one I linked on wikipedia.
The Gallica scans are linked in the wikipedia article. Each of those chapters has hundreds of pages.
I highly doubt that you eye scanned thousands of pages in French handwritten and mixed typesetted ... within less than a day. You definitely must be lying, they take months to read.
[1] https://ionathan.ch/assets/images/angzarr/Berthold%201900.jp...
I went through a bit of it and saw no instance of the symbol. If it's in there, would you mind saying which chapter and which page? Or some hint about what context people could find it in? The maps I saw (maps were pretty easy to find, too, since most of the page numbers for them are "NP") didn't seem to use this symbol.
> Neither the wikipedia page for the Didot family, nor for Histoire générale des voyages shows the Angzarr symbol, I've carefully checked on all the scans on these pages.
You have linked these two Wikipedia pages[1][2], implying that they confirm your extraordinary claims of how obvious and well-known this symbol is. I could in fact check within a single day that the symbol does not appear on any of the 15 images linked in these pages.
So unless you can produce evidence for your claim that "that symbol was used as a notation symbol in those star charts and azimutal maps?", it is quite disingenuous to expect anyone to take it seriously. Expecting someone else to read "thousands of pages" to confirm or deny YOUR claim makes it even less worthy of consideration.
If you do have actual, material evidence for your claims, everyone in this thread would very much like to see it.
[1] https://en.wikipedia.org/wiki/Didot_family [2] https://fr.wikipedia.org/wiki/Histoire_g%C3%A9n%C3%A9rale_de...
Yeah but did any of the four previous articles say anything about it?
There is a combining character that, by its description, sounds like it should be implemented to do the desired thing (U+20DD Combining Enclosing Circle), but my fonts don't render it very well when I stuff geometric characters matching the PlayStation buttons into it.
Without spaces: △⃝□⃝×⃝○⃝
With two spaces between each one so you can see how "enclosing" is getting interpreted: △⃝ □⃝ ×⃝ ○⃝
For the Markdown renderer I'm working on to replace WordPress for my blog, I resorted to shortcodes which resolve to CSS styling the `<kbd>` tag with `title` attributes to clarify and the occasional bit of inline SVG for things where I didn't want to specify a fixed font to get sufficient consistency, like PlayStation button glyphs.
(In all fairness, it's a nerd-snipe made based on the idea that I'll be more willing to blog about things I have nice tools for. I don't currently typeset button presses in any form.)
I don't know if that's a good reason to push to standardize controller glyphs to Unicode, though.
(ETA: Plus the other obvious reason more games and game engines are bringing in full Unicode support is localization, especially for Arabic and CJK. We're a bit past the point where AAA games only feel a need to support EFIGS. The Middle East and Asia are huge markets, especially for mobile games.)
...though, given the inconsistent naming of consistently laid-out buttons, I think anything that makes its way into Unicode should include something that follows the lead of what Batocera Linux does on their Wiki and with custom emojis in their Discord.
See https://wiki.batocera.org/configure_a_controller for an example of how they look inline but the gist is that it's an outline of the SNES-originated diamond of action buttons that pretty much everyone but Nintendo uses these days and which is embodied in XInput and the SDL Gamepad API, with one of the circles filled in to represent the button in question.
