Mat:

> The tick is OK (with my keyboard)... but the anglequote and toolbarbuttons 
> etc... not good IMO...


PMario:

> For my own keyboard I need to compile custom windows settings without 
> "dead" keys to get "ticks", "backticks" and others in a convenient way.


TonyM:

> ... shortcuts may vary with keyboards and languages ...


TT: ยง is on Italian keyboard on touchscreen PC for Windows. But not for  
either English or Extended English. The PMario tick isn't on any of them. 

*Background*. (1) Smallest screen size has changed since MarkDown & 
WikiText was invented (result: different "quote" characters are a problem 
READING on a small screen); (2) Available characters have changed with the 
vast expansion of font support for the even vaster Unicode expansion; (3) 
Most keyboards are now onscreen (Android); (4) These developments SHIFT 
focus from "what does the user's keyboard support?" to "__what do the 
user's fonts support?__" (i.e. a lot of the time a usable glyph CANNOT be 
accessed through a simple keyboard but only through fetching it via a 
program); (5) Most characters from old USA/European keyboard approach are 
eaten-up for markup, WikiText is struggling to find the remainders.

Okay. That is a lot of contentions. But I think broadly right.

SO how to choose workable markup characters for PMario's WikiText 
Extension? I'll write about my experience next.

Best wishes,
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/dd12dfaf-53a1-4e6e-b627-7926dbe8f304o%40googlegroups.com.

Reply via email to