Markdown file can not show exactly when ``` start or end with a blank line

[lotus-king]

• Gitea version (or commit ref):
  latest version
• Git version:
  2.3
• Operating system:
  CentOS
• Database (use [x]):
  • [ x] MySQL
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
    put this markdown file https://try.gitea.io/lotus-king/tls/src/master/openssl.md to gogs or gitea, will reporduce the bug.
• Log gist:

Description

put this markdown file https://try.gitea.io/lotus-king/tls/src/master/openssl.md to gogs or gitea .
gogs or gitea cannot correctly show the markdown file, it just show the markdown source file at code (``` start or end with a blank line) ,but github can show it correctly.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[bkcsoft]

@lotus-king could you try running it through blackfriday directly and see if that works? otherwise it's an upstream bug 🙁

[lunny]

This is not resolved by #186 also. @andrew-boyarshin :) let's move it to v1.2

[andrew-boyarshin]

@lunny If I'm not very much mistaken I've already pointed out that this markdown file has multiple issues and blackfriday is not responsible for fixing invalid markdown.

[ethantkoenig]

This issues seems to be fixed (https://try.gitea.io/ethantkoenig/sandbox/src/master/README.md). Someone please close

[lunny]

see https://try.gitea.io/lotus-king/tls/src/master/openssl.md, it seems the problem is not fixed?

[ethantkoenig]

@lunny As far as I can tell, that's how it should be rendered. I don't see any ``` blocks that aren't being rendered.

[lunny]

It ignored " ```".

[ethantkoenig]

@lunny Oh, I see

[bkcsoft]

It misses it because of invalid indentation. See https://try.gitea.io/bkc/tls/src/master/openssl.md and specifically https://try.gitea.io/bkc/tls/commit/c22378418a700bba1380581be58dc04320b29340

Closing as NotABug 🙂

[lunny]

@bkcsoft But github could render it correctly.

[bkcsoft]

@lunny GitHub is not using the same markdown renderer as we do, and in any case it's an upstream issue and not an issue with Gitea itself. And the point still stands that the example given is invalid syntax (invalid indentation)

[lunny]

@bkcsoft OK.