Mario, Thanks for your focus on this. I have read this response in detail and appreciate you knowledge and effort.
A few Questions and comments - With the use of pragma to introduce or exclude various parsing rules can we choose to apply it to a given tiddler through the import variables in a conditional list withing the view template? Although I see that the space may allow to load it with more possibilities. >> >> - I am yet to grasp the use of trailing "space space enter" >> >> That's compatible to the new "CommonMark" markdown parser spec for "hard > linebreaks". So if someone copies a markdown paragraph to TW, they should > see the same result. > see: https://spec.commonmark.org/0.29/#hard-line-breaks > <https://www.google.com/url?q=https%3A%2F%2Fspec.commonmark.org%2F0.29%2F%23hard-line-breaks&sa=D&sntz=1&usg=AFQjCNE6_-4KyH0jXCqjZ2QWvoCM0LbWKw> > > .. (I just found out, that it's not 100% compatible, but good enough to > start with) > Ahh, I appreciate your keeping these larger parsing issues in mind. > This rule is also intended to work with TW syntax like: > > * test > next line should be part of the li-element. > > *Are you suggesting this?;* - test next line should be part of the li-element. *should become * - test next line should be part of the li-element. *If there is a trailing "space space enter"?* Please see some sample wiki text below that illustrates some of my observations * List :notes * list more :more notes # List :notes # list more :more notes **item 1 no matching"*" Eroniouse dot to left **item 2 <ul><ul> <li>item 1 no matching"*" no eroniouse dot to left</li> <li>item 2</li> </ul></ul> :::*List items indented :::*list With the current Wikitext rules I observe the following issues with bullets - I often follow one or more * with one or more : colons to provide additional lines under a bulleted list items however this screws up ordered lists, in many editors a <ctrl-enter> inserts a line break that does not stop the li element. Perhaps there is a better way - We can use ":" as an indent but perhaps this is breaking some rule? - To add additional line under a `<ul><li>` - To indent before `<ul><li>` > I think, it should be possible to "remove" empty lines or empty lines > preceded by a dot from the generated DOM. At the moment empty p-tags are > created. They are not visible, but they are there, which isn't nice. > > Yea, I did think about that. ... But there will be a steeper learning > curve, the more elements we add or change from the original behaviour. > I think my point here about notes etc.. rather than add elements, allow bespoke elements to be added and where possible provide an extensible element to keep it as simple as possible. There would be a fair argument that a high percentage of content in tiddlywiki's remain within the wiki in which it is written. So I hope that universalising markup so that the content is freely sharable, does not reduce the choices of the author to introduce bespoke methods. But of course such bespoke markup will appear but not evaluated in exported text. <section> and <div> should be no problem, because they allow "flow content > <https://developer.mozilla.org/en-US/docs/Web/HTML/Element/section>" as > "Permitted Content" see the link. > <span>'s are inline elements only. They only allow "phrasing content > <https://developer.mozilla.org/en-US/docs/Web/HTML/Element/span>" (same > as paragraphs). It will produce invalid html code if used at the start of > the line like: * or # or . > > I was thinking about an <aside> (note) using > at the beginning of the > line. > I have some more thoughts here, I will post a separate response. > > \startheading 5 > This is a nice idea, how will it effect transclusions, Actually applying this to subtiddlers transcluded at a different heading level could be helpful, again can we programmatically apply pragma? I also think, the manual workflow could be improved, using less time and > getting improved html output. ... BUT I'll need to think about this. ... I > think about new editor-shortcuts, > That can speed things up significantly. > I am all for this and happy to contribute new editor toolbar buttons, because that is well within my skill level. The idea of a tool to add leading periods to every line, but also one to remove multiple empty lines as suggested by you. Actually I can see a set of optional editor toolbar buttons dedicated to "Cleaning" tiddlywiki content. Or on CSS to to minimise etc... -m > PS: I'll need some time, since the last storm knocked over some of my > trees. I have to remove them. > We have also had storms wind and heavy rain in sydney of the back off our recent fires. Nature will not let us rest. Regards Tony -- 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/47c5e2f7-5ad5-428f-bb04-7ccf7b09e753%40googlegroups.com.
