here is an example of the glyphs that I'm talking about:
https://www.compart.com/en/unicode/search?q=bold#characters
I was wondering if it is because these glyphs aren't supported in the version of unicode that this is in?
Lets you create your own TTF fonts out of pixel font images! · By
here is an example of the glyphs that I'm talking about:
https://www.compart.com/en/unicode/search?q=bold#characters
I was wondering if it is because these glyphs aren't supported in the version of unicode that this is in?
There appear to be some issues with specific character ranges but I’m yet to figure out whether this is an issue on my end (some characters in JS are actually two “surrogate pair” characters) or a limitation of font generator library I use.
You can try opening the font in FontForge to see where did the glyphs go
OK, this is really weird. I went to see where the glyphs went this time on these characters that didn't work, and they are labelled on glyphs that... aren't what they are.
like, "𝕊" is labelled as "핊" instead
I used 𝔸𝔹ℂ𝔻𝔼𝔽𝔾ℍ𝕀𝕁𝕂𝕃𝕄ℕ𝕆ℙℚℝ𝕊𝕋𝕌𝕍𝕎𝕏𝕐ℤ𝕒𝕓𝕔𝕕𝕖𝕗𝕘𝕙𝕚𝕛𝕜𝕝𝕞𝕟𝕠𝕡𝕢𝕣𝕤𝕥𝕦𝕧𝕨𝕩𝕪 here
ones like "ℂ" seem to be labelled correctly though
Someone else confirmed that glyph codes don’t come out right and I confirmed that I’m sending this right, so this is on the font generator library side. See other topic if you’ve got some time to spare.
Also, whatever this is, I guess it’s not uncommon: