problem with <H*> tag conversion

[adueck]

A space is required after hashtags to make the conversion for <H*> tags work. Normally this is not required for markdown converters.

input:

### this works

result:

<H3>this works</H3>

input:

###this doesn't work

result:

###this doesn't work

[kevinsawicki]

This package uses https://github.com/chjj/marked to generate the HTML so you might want to open an issue there.

Normally this is not required for markdown converters.

That is interesting, GitHub requires the space, what converters are you using that don't?

[hemraker]

Hey there
I'm experiencing the same issue. Github does not require the space.

Same file with markdown-preview:

[markuskonrad]

For me it looks like a GitHub feature. Based on Grubers original dokumentation, the whitespace is requried.

Also GitHub describes that in their markdown-basics.

[hemraker]

They certainly have a space in the example 😄

But it is not specific to Github, many markdown editors/parsers support it such as WMD (stack overflow), StackEdit and MacDown.

[adueck]

Thanks for the interest in this. Just for information's sake: I had been using markdown with Jekyll, and have never used the space, so it kind of threw me off at first. But yes, could very well be required with other converters.

[leipert]

The CommnMark Specification also says, you should have a space, to avoid stuff like this:

# Header

I want to tell you about issue
#5, it is our priority  <-- no headline

[hemraker]

@leipert : I agree, the space is best practise but not supporting a thing that is used widely AND is supported by many converters seems like a shortcoming. If you don't get the correct preview then it is not really a preview.

I had to switch to another package because markdown preview doesn't give a correct representation of the files I'm working with.