Ciao Mat Far be it from me to actually know the solution :-).
But I could imagine an additional JS "Custom Parser" that would let you pass through regular expressions that would recognise and render "Custom Markup." This could be more than one. No reason why one Custom Parser might not do a few. I'm thinking of things like ... On start of line (a <p>) = ".." > Renders as = "indent para 2rem left and right" (<p > class="tw_custom_my-indent">) The difficulty would be understanding "inter-actions" with extant wikitext and the parsing process. I doubt that could be core. But I think it should be well possible via plugin. Best wishes TT On Sunday, 29 December 2019 20:11:17 UTC+1, Mat wrote: > > @TiddlyTweeter wrote: >> >> The major barrier being that the main parsers are in JS which is not >> transparent to most of us. >> > > I'm thinking that since we do already have some strings that are converted > (i.e we have wikitext) then the method applied for this conversion could > perhaps be made general to use placeholders for input strings and what/how > it outputs. The user could list all his custom wikitext in some kind of > dictionary... specifying the custom input strings (start and end strings) > and their "translation". It is also necessary with some security checks so > that the user doesn't attempt to overwrite critical commands. > > <:-) > > -- 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/ce192407-97de-4919-84ae-de0aff944e63%40googlegroups.com.
