http://qs321.pair.com?node_id=1153837


in reply to Re: Good Intentions: Wikisyntax for the Monastery
in thread Good Intentions: Wikisyntax for the Monastery

> LanX it does not work for nested tags?

It does , but currently only for one word. (see the regex singleword in the code)

The problem are longer strings, the number of misinterpretations will occur far more often if one allows more than 1 word. Where do I have to draw the line? 3, 4 words ...?

I was thinking of using doubled symbols like ** instead of * for longer passages, like in wikicreole

The goal is to make the syntax rules customizable for the user.²

In the end <b><i><u> are not really that important, the other features are far more relevant when typing on a mobile device.

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

update

Thanks for your interest and contribution! :)

footnotes
²) did I mention my to-do list ? ;-)

Replies are listed 'Best First'.
Re^3: Good Intentions: Wikisyntax for the Monastery
by Discipulus (Canon) on Jan 28, 2016 at 12:55 UTC
    Also
    'ARGV'<br>
    seems not to behave correctly: just to add to todo list

    your code is in production for me anyway

    L*

    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.
      Thanks for your feedback!!! :)

      > 'ARGV'<br>

      But you forgot surrounding spaces. It has to be  'ARGV' nextWord -> ARGV nextWord

      Please note: The rule for this wiki-syntax is

      Space MarkUp Word(s) MarkUp Space ³

      otherwise I'd think it's a test would cause "Id think its a test" ²

      BTW: I rarely use <br> anymore, just use an empty line to force a <P>aragraph. I don't think <br> is worth an own wikisyntax

      Side-note

      stackoverflow uses `...` for inlined code, I was thinking of adapting this, but backquotes are too "hard" to type on a mobile and I quickly got used to only use "..." (i.e. double quotes) for "real" quoting. Of course this is a matter of taste and should be customizable too.

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)
      Je suis Charlie!

      ²) what I actually typed in this post was   'I'd think it's a test' please note how the surrounding whitespace worked to create a code area without conflicting with the apostrophes.

      ³) there are issues with whitespace at the beginning and ending of lines and textareas, this is largely due to browser incompatibilities. I just stopped worrying and started to add extra spaces where needed.