Revision history  [back]

Looks like there are inconsistencies between the markdown renderers in previewer (and maybe errors within), previewer, there isn't an easy fix I'm afraid, b/c only extensive testing can validate a parser well.

What you suggest - giving a warning on use of special characters - might work actually and can be done.

The workaround is to use backticks around the inlined literals or four leading spaces on each literal line. That's the official markdown for the snippets of code.

You can also select the text you want to post as a literal snippet and then hit the "preformatted text" button (the one with one's and zeroes) or a combination of keys Ctrl-K.

The reason things with angle brackets "disappear" is that markdown does allow HTML tags, however markdown parsers do not perform full input validation and do not give warnings on edge cases.

I will put out better tooltip help for markdown - looks like people need better heddukation - and try to add an alert like you've suggested.

Looks like there are inconsistencies between the markdown renderers in previewer, there isn't an easy fix I'm afraid, b/c only extensive testing can validate a parser well.

What you suggest - giving a warning on use of special characters - might work actually and can be done.

The workaround is to use backticks around the inlined literals or four leading spaces on each literal line. That's the official markdown for the snippets of code.

You can also select the text you want to post as a literal snippet and then hit the "preformatted text" button (the one with one's and zeroes) or a combination of keys Ctrl-K.

The reason things with angle brackets "disappear" is that markdown does allow HTML tags, however markdown parsers do not perform full input validation and do not give warnings on edge cases.

I will put out better tooltip help for markdown - looks like people need better heddukation - and try to add an alert like you've suggested.

Looks like there are inconsistencies between the markdown renderers in previewer, there isn't an easy fix I'm afraid, b/c only extensive testing can validate a parser well.

What you suggest - giving a warning on use of special characters - might work actually and can be done.

The workaround is to use backticks around the inlined literals or four leading spaces on each literal line. That's the official markdown for the snippets of code.

You can also select the text you want to post as a literal snippet and then hit the "preformatted text" button or a combination of keys Ctrl-K.

The reason things with angle brackets "disappear" is that markdown does allow HTML tags, however markdown parsers do not perform full input validation and do not give warnings on edge cases.

I will put out better tooltip help for markdown - looks like people need better heddukation - and try to add an alert like you've suggested.

Looks like there are inconsistencies between the markdown renderers in previewer, there isn't an easy fix I'm afraid, b/c only extensive testing can validate a parser well.

What you suggest - giving a warning on use of special characters characterse - might work actually and can be done.

The workaround is to use backticks around the inlined literals or four leading spaces on each literal line. That's the official markdown for the snippets of code.

You can also select the text you want to post as a literal snippet and then hit the "preformatted text" button or a combination of keys Ctrl-K.

The reason things with angle brackets "disappear" is that markdown does allow HTML tags, however markdown parsers do not perform full input validation and do not give warnings on edge cases.

I will put out better tooltip help for markdown and try to add an alert like you've suggested.