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/861387d1-7ccc-490e-b75c-b55e76b1ea9bo%40googlegroups.com.

Reply via email to