Mario, It is good to state and restate the current state of play on this one. So thanks for your summary.
I am not sure, but I wonder if we are on the same page, most likely, but it is worth checking on the *original paragraph suggestion;* My feeling this needs to be very precise because its not so easy to express this. This is what is making me unsure, around the \n and \n\n cases; I did create the "Add a new-line at the end of the line" toolbar button, > that will double up every existing \n to convert a marked block of text > into html P tags. Is this so you can take multiple lines and combine them into one paragraph? - so you use \n\n as the end of block "endString"? - Is this why you started using div for blocks because P separated every line? The reason I wanted to do this based on \n only is as follows; - if \n can be used as the end string to create a paragraph, once a paragraph is created there is always a blank line that follows that paragraph, HTML standard with P - if there is a second or third \n, ie blank lines and you apply the same prefix to each then please follow what happens below; Original text Paragraph penultimate paragraph Last paragraph In this example I use 'p to represent the custom tick for paragraph Individually or bulk inclusion of the 'p<spaces> to every line gives 'p Paragraph 'p 'p 'p penultimate paragraph 'p Last paragraph Becomes on render <p>Paragraph</p> <p></p> <p></p> <p>penultimate paragraph</p> <p>Last Paragraph</p> And is displayed as Paragraph penultimate paragraph Last paragraph ie: multiple blank lines are collapsed to a minimum of 1 blank line, missing blank lines become a minimum of 1 blank line (are added in the HTML render step by the rules of html P) It seems to me that my use case exclusively needs only \n as the end string, it's when you wish to block format such as a div that this changes, and where we may want to have an alternative end string such as \n\n, - Are you placing "\n\n" in the content effectivly so you can use it as an end string? - Or Can you NOT rely on the \n\n in the content in many cases, thus you need to add it? Given we can now specify the end string, perhaps the default behaviour should be endstring "\n" on newlines (visible or not). After all this is what confuses everyone new to tiddlywiki, ie when using line based wiki text the line feed is honoured eg * # ! a newline is created, but any "free text" ends up concatenated with the content above and the (first) new line hidden. It seems to me that given the value of a 'p to resolve this issue, with line breaks, *just as every other wikitext special character does as well,* - but in this case on any/every line then this should be a primary focus, - with the \n\n cases only secondary? Restated, we need to fix the fact that in the editor This is a line or paragraph This is another line or paragraph Automatically becomes This is a line or paragraph This is another line or paragraph And This is a line or paragraph This is another line or paragraph *Looks the same after render* Note: There is no way to display this as entered (without workarounds) This is a line or paragraph This is another line or paragraph I have chosen to use paragraphs to help when the content has many extra line breaks, but other html tags will deliver the output as seen in the editor text. - Note this is \n in action not \n\n I hope this is clearer. As a mentor once said to me if you perceive a problem then consider some possible solutions then come to me with the "problem and possible solution", not just the problem. So I will try. Thanks Tony On Saturday, 12 September 2020 00:28:47 UTC+10, PMario wrote: > > On Friday, September 11, 2020 at 3:58:51 PM UTC+2, @TiddlyTweeter wrote: > > 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'm thinking about a possibility to disable the markup on a "per ID" > basis. So it may be possible to say: > > \rules except customtick customdegree > > To disable elements per tiddler. Or to use the ControlPanel : Info : > Advanced : Parsing tab. .. At the moment there is only ticktext which will > disable all of them. > > We do have > - 3 pragma rules: customize , debugcustomize, importcustom > - 1 inline rule: tickinline > - 1 block rule: ticktext > > The block rules should be > > - customtick > - customdegree > - customcomma > - customunderscore > - customangle > - customtilde ..... may be I'll this one as default endString \n\n too > > I need to have a closer look if that's possible, without duplicating any > code js. > > -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/7490e67a-477d-47df-b241-61e49cda0df6o%40googlegroups.com.
