Why isn't MarkdownSharp encoding my HTML?

后端 未结 3 1392
野趣味
野趣味 2021-02-20 14:48

In my mind, one of the bigger goals of Markdown is to prevent the user from typing potentially malformed HTML directly.

Well that isn\'t exactly working for me in Markdo

3条回答
  •  终归单人心
    2021-02-20 15:47

    Maybe I'm not understanding? If you are starting a new code block in Markdown, in all its varieties, you do need a double linebreak and four-space indentation -- a single newline won't do in any of the renderers I have to hand.

    abc -- Here comes a code block:
    
        
    This is code

    yielding:

    abc -- Here comes a code block:

    This is code

    From what you are saying it seems that MarkdownSharp does fine with this rule, so with just one newline (but indentation):

     abc -- Here comes a code block:
         
    This should be code

    we get a mess not a code block:

    abc -- Here comes a code block: This should be code

    I assume StackOverflow is stripping the

    tags, because they think comments shouldn't have divisions and suchlike things. (?) (In general they have to do a lot of other processing don't they, e.g. to get syntax highlighting and so on?)

    EDIT: I think people are expecting the wrong thing of a Markdown implementation. For example, as I say below, there is no such thing as 'invalid markdown'. It isn't a programming language or anything like one. I have verified that all three markdown implementations I have available from the command line indifferently 'convert' random .js and .c files, or those inserted into otherwise sensible markdown -- and also interpolated zip files and other nonsense -- into valid html that browsers don't mind displaying at all -- chicken scratches though it is. If you want to exclude something, e.g. in a wiki program, you do something further, of course, as most markdown-employing wiki programs do.

提交回复
热议问题