Mario,Josiah ¶ I would not bother with the use of pilcrow unless it was part of an end of line form of glyph only. Its key use would be to place a pilcrow in a large slab of text to force a pagarapgh break. if other glyphs depended on \n\n, it would be best to resolve these first if possible. There is a implied *new paragraph* that follows the ¶ that is sufficient in my view (as for this paragraph). If one was to have a start and end the appropriate method is a revers-pilcrow and pilcrow pair.
End of line only mark up, with selectable glyphs, Would allow someone like > me to define a glyph "¶" as "<br>br>" so insertion of ¶<space> would > render as a new paragraph "break". This provide the complement to beginning > of line and inline mark-up. Arguably the ¶ could be given a definition that highlights the first word of the next (generated paragraph). Josiah, I don't mind decent, however I disagree with the lack of visibility with "the" parenthesis, and value how the look. First with Custom wiki text present they disappear in the output. Secondly we can use the slightly different examples given. My point here is if something is not good enough ⸨rather than exclude it⸩ find if there is a way to 〖 address 〗 it, such as ⁽ Here ⁾ or ₍ there ₎ remember as a rule already text contains ' " ` and other characters even less readable. The fact that a reader may not be able to tell the difference may actually be an advantage when no customisation is occurring. If we have two (or more) open and close braces there is an opportunity to define one as non-operative in text that contains one of the other pairs. The point being the only reason they will be in use is because the writer chooses to. I am actually keen to use such Unicode braces simply to delimit a piece of text, I would write separate macros to extract those ﹤keywords and phrases﹥ so delimited, independent of the current text even without the use of customise. However if such pairs are available to "custom wikitext" further automation or formatting can be done to automate this feature. Tony On Thursday, 29 October 2020 01:53:12 UTC+11, PMario wrote: > > On Wednesday, October 28, 2020 at 1:50:44 PM UTC+1, @TiddlyTweeter wrote: >> >> *Regarding User Possibility To Set Markup Glyphs?* >> >> TonyM wrote: >>> >>> >>> *Question - customised Glyphs, a glyph too far?* >>> >>> - As you can see the wide range of glyphs available that have >>> meaning or structure makes me wish to ask if we could allow the user to >>> nominate glyphs either single (line/para/blocks) or pairs for inline or >>> block. ie customise the customise glyphs. >>> >>> >> Ciao TonyM & PMario >> >> IF this were possible I WOULD use it. >> > > ... need to think about it. But it would make configuration a hell lot > more complex. > > >> Why? Because the kinds of Markup I do would benefit from me being able to >> choose glyphs VISUALLY SUITED to the purpose. >> For instance, for simple paragraphs ... >> >> ¶ Start of a paragraph, >> more of the same pargraph endedon the next line. >> ⁋ <--- End String >> >> I understand if its not possible. >> > > It would be possible to use pilcrows as "start" and "end" of a paragraph, > but I don't understand why. > > TW Pargraphs end with \n\n by default > > So the "reversed pilcrow" ⁋ <--- End String is redundant and for me > personally it is confusing, since Libre Office and Word use: ¶ as a > paragraph marker. ... It may be wrong, but it is shown at the *end* of a > paragraph. ... So the reverse pilcrow feels completely wrong at that > position. > > *I could implement:* > > ¶ some text \n\n > > Since it would be the right thing to do. see: Wikipedia Pilcrow > <https://en.wikipedia.org/wiki/Pilcrow>. It would be easy to explain, > with the link to Wikipedia. It will create a HTML P tag by default. > > If you want you can define an _endString. ... Default would be \n\n > > -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 tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/efb10bf8-eba1-4cea-8fc5-36b85f83266fo%40googlegroups.com.
