Ciao PMario My point before that we have REDUNDANT characters so we can address internationally a user can use some not all. They chose for EACH MAIN MARKUP between two options. Portability would be adequate
I will comment separately on "escape". *The BASIC issue is this: *Getting stuck in a limited approach to keep Euro keyboards happy could damage code thinking. You get the point? Ask if its not clear. I'm sure we can work round it. Best wishes TT On Friday, 11 September 2020 14:43:56 UTC+2, PMario wrote: > > On Friday, September 11, 2020 at 2:26:53 PM UTC+2, @TiddlyTweeter wrote: >> >> In haste, PMario & TonyM >> >> TonyM wrote: >>> >>> Mario, >>> >>> - I think it is worth persisting before release so we do not >>> compromise the future possibilities >>> >>> I agree. PMario opened a lot of doors. We need time to go through them >> to TEASE out the power yet ensure workable default behavior. >> ONE thing on my mind is INLINE nesting. Current *@@ ... @@ *prevents it. >> I'd like time to show how a markup inline of »...« could support it and >> correct closure of inlined elements. So »tag-A ...»tag-B ...«« get >> closed correctly. >> > > As I wrote, we can't use single angle quotes, since they are part of > standard prose text in some countries. > > Both forms are standard like: > *»some quoted text«* and *«some quoted text»* in different countries. .. > We will need to use double-something. > > It may be possible to detect: *°°a* some text °°b nested text °°b *°°a * > ... May be! > > -mario > -- 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/669ced88-24ab-4141-9bbf-8dd7e64c1c71o%40googlegroups.com.
