🚀 go-pugleaf

I think using the Windows calculator is a perfectly acceptable way to convert between hex and decimal :)

Here's another issue:
there are two stages to getting a unicode character to display: you have to specify the correct character, and then the font involved has to actually have a glyph for that character in it.

I expect, to put it rather anthropomorphically, it goes something like:
1. you type/paste the character
2. Application asks the font if it has a glyph for that character
3. If not, application asks operating system if it has a font that has that character
4. Once one is found, it gets displayed.

My hunch from what I've seen is that applications like Word, and most web-broswers these days, will liase with the Windows operating system until a font is found that has the necessary glyphs for the required characters.
However, some applications give up at step two: if, for example, your doc in some Adobe application is using Helvetica, and you ask for a very obscure unicode character, and Helvetica doesn't have a glyph for it, you may just get a blank square or "Missing character" symbol.

This used to also be the case with the Firefox browser - if I was writing a webpage and put in an obscure character, which wasn't present in default fonts like "Times New Roman" or "Verdana", I'd get a missing character symbol instead, even though my PC had other fonts which *did* have glyphs for that. I'd need to explicitly put "font="Arial Unicode" or sthg like that into the webpage to make it talk to windows to retrieve a glyph.
However, over the past couple of years, Firefox has stopped this and will just go get whatever glyphs it needs.

Perhaps programs like Frame and InDesign actually see this kind of behaviour as a virtue?

(All the above is totally speculative based on my own experience, mind you...)