Unsupported/not yet supported Markdow features

[pfalcon]

Things to support (checked - supported, unchecked - unsupported):

• [x] Checkbox lists
• [ ] Multilevel lists with arbitrary indentation (seems that Zim requires a tab as indentation for each level of a multilevel list).
• [ ] Unordered bullet lists with - as a bullet (* is supported so far)
• [ ] Superscript/subscript (Zim native syntax should be recognized)

[FernandoBasso]

I have been using a Notebook with Markdown for about a week now and it has been working fine. Your work is much appreciated! Thanks a lot for this effort.

[pfalcon]

@FernandoBasso: Thanks for the feedback, glad it's working for you!

[Korodny]

I assume Github flavoured Markdown is the standard you're aiming for?

While Github's "fenced" code blocks (three backticks above and below a block of preformatted text) are supported, original Markdown's approach - which is also supported by Github - of indenting a paragraph by four spaces to mark it as preformatted text is not supported. That would certainly be nice to have.

Of course, supporting quoted text would be very nice as well, but that would require changes in the official branch, so this is impossible for now.

[pfalcon]

I assume Github flavoured Markdown is the standard you're aiming for?

I'm not really aiming for anything, except for having a tool to maintain my Markdown-based personal knowledgebase. I originally wanted to write such myself, but then found Zim, which had nice UI, but was completely useless to me with its proprietary text format. So, I hacked up some Markdown support on top of it (enough for me), and that get me much further than if I wrote a thing from scratch. But neither my hack nor the underlying Zim itself is anything like perfect. I'm more or less ok with that, as for me the most important is my data (and access to it), not a tool. Surely, I'd like to improve the tool, but likely that would take someone else to join in and push along...

While Github's "fenced" code blocks (three backticks above and below a block of preformatted text) are supported, original Markdown's approach - which is also supported by Github - of indenting a paragraph by four spaces to mark it as preformatted text is not supported. That would certainly be nice to have.

I personally don't miss that. And as I mentioned elsewhere, a proper way to resolve things like that would be to plug in a proper Markdown parser (external module).

Of course, supporting quoted text would be very nice as well, but that would require changes in the official branch, so this is impossible for now.

Ack, that's what I miss myself, and would look into one of these years.

[rc-mfierro]

This has been a lifesaver, thanks @pfalcon for the time you've put into this! Block-quotes don't work exactly the way I had expected though, are they an officially supported markdown tag?

[pfalcon]

I'm using both

`foo`

and

```
foo
```

here.