On Wednesday, March 4, 2020 at 12:01:57 AM UTC+1, TonyM wrote: > > Mario, > > >> I just found out, that we can't use a "global" dot-paragraph rule since >> it messes with the TW stylesheet parsing. eg: >> >> > > Maybe this the point. Such bespoke parsing could be designed to only > operate for a given tiddler type >
I don't really want to go that route. There is a pending issue by Jeremy <https://github.com/Jermolene/TiddlyWiki5/issues/345> from 2014 and a PR by BJ <https://groups.google.com/d/msg/tiddlywiki/EVITIZd-UgU/1E1QSk-rEwAJ> also from 2014. http://bjtools.tiddlyspot.com/ contains some related stuff from 2016 which uses MIME-type parameters like: "text/vnd.twbase;flexibility=MDL ... The problem with such params is, that they need to be fully specified at the time, they are registered. ... Which will probably never happen with TW. > or tiddlers with the pragma set to apply the "local" parsing rule. > I think, that would be the faster way. ... I can't use \rules use xxxx since it would need to overwrite :/ the core wikiparser.js, which is the main wikitext parsing function. As an example In the case of the dot paragraph The key places I would > expect to use it would be > > - when pasting text from other sources and transforming to a more > readable rendering > - when typing content in class or capturing ideas brain to text > > In these examples I would be happy to introduce pragma to support this > \bespokemarkup notes > \bespokemarkup dotparagraphs > where notes defines standard markup + some rules defined in "notes". > yup... Since I have to use a new pragma anyway eg: \parserule dotparagraph <setting> ... or something similar, there will be much more new code involved, as I wanted it to be :/ > > - Although a way to apply it from the view template or another > conditional method would be nice. > > I think, that's not possible since the ViewTemplate depends on the parser settings already. Parsing is done way ahead of rendering. Everything, which needs to be decided at viewing time needs to be a widget. > > - The point being you would not do this on a tiddler containing CSS > unless it provides some value. > > That's right. I found out about the problem, while experimenting and suddenly some "custom CSS" ceased to work. > > - In tiddlywiki a local rule can become global if you apply it > everywhere but I think bespoke markup could be constrained to nominated > tiddlers. > > I "kind of like" this downside, since it will add some info eg: \parserule ... at the top of the tiddler, that won't be "parsed" if copy pasted to a different TW. So users will have a clue, what to do. Users also have the choice to ignore and delete the pragma, if they want. > The point here is I / We are free to use period and I do not need to go > looking for other symbols. > :) ... I personally didn't like the leading dot BUT I do see, that having it that way may be essential for other users. ... I'll try to make it configurable. For the time being I'll attach an experimental zip file here with a global hack, that uses dot-space, which shouldn't have side effects. So you can play with it. Attachment will follow soon. -mario -- 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/e5a9a34a-e954-4d99-8e44-42da0d49c576%40googlegroups.com.
