lruiz/MarkdownPapers

Rendering issues

orefalo opened this issue · 5 comments

I was testing your engine and found multiple differences with other implementations:

Especially this one http://joncom.be/experiments/markdown-editor/edit/

The resulting html, when processed with markdownPapers is slightly different.

Here is the test document I am using

Syntax Cheatsheet

Phrase Emphasis

italic bold
italic bold

Links

Inline:
An example

Reference-style labels (titles are optional):
An example. Then, anywhere
else in the doc, define the link:

Images

Inline (titles are optional):
alt text

Reference-style:
alt text

Headers

Setext-style:

Header 1

Header 2

atx-style (closing #'s are optional):

Header 1

Header 2

Header 6

Lists

Ordered, without paragraphs:

  1. Foo
  2. Bar

Unordered, with paragraphs:

  • A list item.

With multiple paragraphs.

  • Bar

You can nest them:

  • Abacus
  • answer
  • Bubbles
  1. bunk
  2. bupkis
    - BELITTLER
  3. burper
  • Cunning

Blockquotes

Email-style angle brackets
are used for blockquotes.

And, they can be nested.

Headers in blockquotes

  • You can quote a list.
  • Etc.

Code Spans

<code> spans are delimited
by backticks.

You can include literal backticks like this.

Preformatted Code Blocks

Indent every line of a code block by at least 4 spaces or 1 tab.
This is a normal paragraph.

This is a preformatted
code block.

Horizontal Rules

Three or more dashes or asterisks:




Manual Line Breaks

End a line with two or more spaces:
Roses are red,
Violets are blue.

Could you send the test document to my email?

Hi, I didn't receive the email, :(

Hi, here my findings

Rulers are not recognized if they are not followed by an empty line

- - - - 
## Manual Line Breaks

References are not overrided when they are declared more than once, taking the first ocurrence

[id]: http://example.com/  "Title"

... and later 

[id]: images/markdown-icon.png "Title"

Headers are not recognized if they are not preceded by an empty line

Setext-style:
Header 1
========

We got to the same conclusion, but how do you explain that the html generation above works fine ?

See, it's all about sticking to one md specification, just like the ** issue we discussed last week. I am pretty sure Digg uses the same conventions as github... the document should render properly.

-> except for the [id] stuff which is a valid mistake.

Yes, It works fine, minor rendering problems.

I think I can improved some things here (or align to what most implementations do) at least the Ruler detection should be fixed.