Add support for `<nowiki>`

[Jermolene]

There is currently no convenient way to write ordinary text without it being inadvertantly wikified. For example:

svn://example.com
__stdcall

The double slash is interpreted as the start of an italic run, and the double underscores are interpreted as the start of an underlined run.

We should add support for <nowiki> which would enable:

<nowiki>
svn://example.com
__stdcall
</nowiki>

I am not keen on the <nowiki> syntax because it misleadingly looks like an HTML element, but isn't treated as one.

One possibility might be to extend the current hardlinebreak syntax so that it also prevents wikification:

"""
svn://example.com
__stdcall
"""

[pmario]

There is the

\rules except emphasis

which does the trick, but it disables all of them. ... So it would be nice if the emphasis.js module would be split up into several modules, so one could say:

\rules except underline
\rules except bold
\rules except strikethrough
...

[Jermolene]

Hi @pmario good idea, perhaps worth a separate ticket?

[pmario]

see #701

[tobibeer]

+1

for...

"""
foo
bar
"""

or

<nowiki>
foo
bar
</nowiki>

because...

\rules except ...
disables all of them

is not quite desirable

[Jermolene]

Hi @tobibeer

a) We've already implemented triple double quotes for hard line break blocks.

b) @pmario's suggestion about splitting the emphasis rules up has already been done in #701

So, are you suggesting that we also implement the <nowiki> syntax? I'm against that syntax because it looks like an HTML element but isn't parsed as one.

[tobibeer]

Perhaps an interesting read for opening up custom elements...

According to the HTML specification:

The HTMLUnknownElement interface must be used for HTML elements that are not defined by this specification.
The same is not true for custom elements. Elements with valid custom element names inherit from HTMLElement.

So, properly declared, this would be perfectly fine:

<no-wiki>
//no
wiki//
</no-wiki>

Alternatively, it could be a widget, if that's the appropriate module, which makes it slightly harder to type...

<$nowiki>
//no
wiki//
</$nowiki>

[Jermolene]

Perhaps an interesting read for opening up custom elements...

I'm actually not at all a fan of custom elements (except for building polyfills), but that's another discussion :)

Anyhow, the issue is that the <no-wiki> pseudo element needs to parse it's content differently than ordinary widgets/HTML elements. Right now all widgets/HTML elements are parsed in the same way.

[tobibeer]

How about a parser escaping contents based on (forward) ticks?

inline

´´´//foo/bar´´´

block

´´´
//foo
bar//
´´´

...rendering contents into a <pre class="tc-nowiki"/> styled like a general p.

[Jermolene]

That would be nice but I can't figure out how to type those forward ticks on a Mac, and I don't think it's possible on the iPhone. I suspect that wikitext should restrict itself to basic ASCII characters.

[tobibeer]

Ok, one last shot for a notation, for now.
I would personally be fine with three of any of these:

'''foo'''
@@@foo@@@
___foo___
~~~foo~~~
\\\foo\\\
///foo///

...and the corresponding block notation.

[tobibeer]

Just noticed, anything resembling an <xml> tag enclosed in wiki markup will screw up the subsequent output, e.g. try...

''<fieldname>''

* some text

[Jermolene]

Hi @tobibeer that's correct. If you type something that looks like an HTML tag then it will be treated as an HTML tag.

If you "inspect element" on your example you'll see what's going on.

[pmario]

@Jermolene

You wrote #699 (comment)

So, are you suggesting that we also implement the syntax? I'm against that syntax because it looks like an HTML element but isn't parsed as one.

and we did implement: splited emphasis.js into several modules to have fine grained control with rules pragma #702

So IMO this issue should be closed