*YES. Do use Unicode Glyphs when they have FONT support in TW!* PMario wrote: > > So ⠪.class:param Braille 246 and Braille 2345⠞ may be an option. > > - So it's Braille: 246 as a start, which seems to be not used by the > default alphabet. > - And Braille 2345, which is letter: t > > They will be hard to type, but can be predefined. .. > > What do you think about: 25 as start: ⠒ and 2356 as stop: ⠶ >
We discussed already the very complex issue of (1) providing markup glyphs that WORK VISUALLY; (2) that are SUPPORTED in default TW FONT assignments. Matching both criterion is not easy. Your discovery that Braiile characters *⠒ & **⠶* would work (be supported by TW fonts) I think brilliant! I think that pair is an EXCELLENT choice. Some may complain that they are not on keyboards. But that applies to most every new markup character. It is simply NOT possible to support new characters on keyboards universally. But all we need is an Editor driven button / or key-combo to solve that subsidiary issue, which is easy. So, I am very in FAVOR of *⠒ & **⠶ *solution. Mainly because it VISUALLY makes sense for markup (*⠒ = open & **⠶ = close*) . They are unambiguous, single characters, VISUALLY elegant. Thoughts TT -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev/af500787-baa0-41ad-939f-dfc7ff652ddbo%40googlegroups.com.
