Ciao TonyM Just some initial comments.
Thankyou for laying out something that is very clear on the final aim. > > Have you seen additional markup before? > Yes. Seen and made. Though I tend to use raw regular expressions via BJ's tool that runs before the main parsers start for that. I don't think that is the best approach here. What is the best way to implement it? > Via a parser under ... $:/core/modules/parsers/wikiparser/rules/ This could be either a hack of an existing one. OR, probably better, by cloning one of the exiting parsers and modifying it. I'm not fully clear on how you run a new parser rather than a hacked one. Or whether it matters what order they run it. But I doubt it is difficult to sort out. The parsers are in JS but I don't think you need much JS knowledge to modify one as the important part will be a regular expression match followed by a replace. > Should this be standard or optional, or a plugin? Probably a plugin. However, I often wordered if it would be worth requestiing that a generic "Custom Parser" be added that a user could add new markup processing for render to. Best wishes TT -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki/1555509f-6a16-45d2-9eb3-76e49573ad16%40googlegroups.com.
