TW Tones wrote: > > > I have discovered that the Unicode standard has additional alphanumeric > characters here https://www.unicode.org/charts/PDF/U1D400.pdf >
Unicode is brilliant. Its an "elusive obvious". One to explicitly use a lot, lot more. The PROBLEM now is not lack of machine support--its the problem of being SURE the glyphs you are using have proper FONT support. This is no problem on local machines because IF you have the glyph in a font on your machine it will show up. The problem is only IF you want to be sure an end user ONLINE can see the glyph. There its more complex. A reasonable route for TW is to check the presence of the glyphs in the fonts listed in TW (mainly Mac fonts in the Empty download?) . This is because one needs to beware of getting confused by the "local machine's" cascade of font substitution. That is exactly where Unicode support can get confusing. FWIW, I use BabelMap to double check that specific TW (Standard Windows 10) fonts contain the needed glyphs IF the TW is destined for on-line. Best wishes TT -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/3b52c279-1c78-4c24-ba2d-1f4c0d1a0988o%40googlegroups.com.
