Ciao PMario & all I been doing a lot of testing of using Custom Markup for layouts and precision CSS application. It is VERY good.
A number of issues came up. I will post about each separately. First I comment about Editor Look & Keys, then Fonts & Unicode. I did testing on English Win7 (DT), Italian Win10 (tablet) & Android6 (standard phone) computers. *1 - EDITOR LOOK & SETUP* *Key Availability *- It became clear quickly that whilst all three system tested on have Font Support they all differ in native Keyboard Support. *None has all 6 IDs available easily on keys.* This just confirms what we said before: *the tool requires buttons, keyboard shortcuts and likely (for boilerplate WikiText) stamp tool use.* The approach PMario took to deal with this via buttons & key shortcuts works well... but ... *Too Many Buttons? - **I think there may be too many buttons :-). *For instance are the buttons that just *remove *an ID needed at all? What is primary is to be able to insert IDs, which it does. But I don't see added value (myself) to remove them where a single "delete" stroke does it anyway! *Button Pictures - *This is ONLY an aesthetics comment; but why not just have a *picture of the single ID* on a button and no more? Visually I think they are over-noisy. 2 - SOME NOTES ON FONT SUPPORT - PMario & I already briefly discussed this. Its not an issue on the 6 IDs, at least not for European languages. But it *is an issue if you want to use Unicode characters in \customize pragma*. I tried to pin down some RELIABLE (typographic) characters available through Unicode (i.e. that have "universal" font support). This is not an easy thing to do. Font substitution behavior of OS' systems (a pretty amazing process BTW) that create "composite" fonts on the fly, using available fonts on the computer can make it near impossible to predict (1) glyphs that will appear in other people's TW; (2) what they will look like (e.g. sometimes coloured, sometimes not, sometimes visually very different). This is obviously NOT directly a TW issue. But it made me wonder whether in fact we (the whole internet) are seriously under-using Unicode that would make life much easier---and not just to better support Custom Markup. My point for TW? I'm wondering IF, we could assemble a *custom font *of say 100 Unicode *typographic *signs (e.g. punctuation marks, markup symbols, reference signs etc) and *EMBED* this in a TW? I don't know how you'd embed it or access the font. But I know how to make such a font set. Q: Is it possible? Your thoughts? 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/64c9e825-5ac7-4bb2-88a9-4ac5ed85b193o%40googlegroups.com.
