Full table syntax not supported #17

New Issue

claunia · 2026-01-29T14:19:59Z

claunia commented

2026-01-29 14:19:59 +00:00

Originally created by @madskristensen on GitHub (Jun 19, 2016).

This syntax isn't treated as a table:

|Milestone|Release Date|
|---------|------------|
|Beta7    | 24 Aug 2015|
|Beta8    | 21 Sep 2015|
|RC1      |    Nov 2015|
|RC2 Pre1 |    May 2016|

Using BabelMark3 I can see that some other parsers render it correctly, like this:

Originally created by @madskristensen on GitHub (Jun 19, 2016). This syntax isn't treated as a table: ``` md |Milestone|Release Date| |---------|------------| |Beta7 | 24 Aug 2015| |Beta8 | 21 Sep 2015| |RC1 | Nov 2015| |RC2 Pre1 | May 2016| ``` Using [BabelMark3](https://babelmark.github.io/?text=%7CMilestone%7CRelease+Date%7C%0A%7C---------%7C------------%7C%0A%7CBeta7++++%7C+24+Aug+2015%7C%0A%7CBeta8++++%7C+21+Sep+2015%7C%0A%7CRC1++++++%7C++++Nov+2015%7C%0A%7CRC2+Pre1+%7C++++May+2016%7C) I can see that some other parsers render it correctly, like this: ![image](https://cloud.githubusercontent.com/assets/1258877/16174749/c489da42-3586-11e6-9b56-83a904e7044b.png)

claunia added the bug label 2026-01-29 14:20:00 +00:00

claunia closed this issue

2026-01-29 14:20:04 +00:00

claunia commented

2026-01-29 14:20:08 +00:00

@xoofx commented on GitHub (Jun 19, 2016):

Indeed, it looks like a trailing | on the header separator is making the table detection not working properly. For example this one is working:

|Milestone|Release Date|
|---------|------------
|Beta7    | 24 Aug 2015|
|Beta8    | 21 Sep 2015|
|RC1      |    Nov 2015|
|RC2 Pre1 |    May 2016|

Will dig into this.

@xoofx commented on GitHub (Jun 19, 2016): Indeed, it looks like a trailing `|` on the header separator is making the table detection not working properly. For example this one is [working](https://babelmark.github.io/?text=%7CMilestone%7CRelease+Date%7C%0A%7C---------%7C------------%0A%7CBeta7++++%7C+24+Aug+2015%7C%0A%7CBeta8++++%7C+21+Sep+2015%7C%0A%7CRC1++++++%7C++++Nov+2015%7C%0A%7CRC2+Pre1+%7C++++May+2016%7C%0A): ``` |Milestone|Release Date| |---------|------------ |Beta7 | 24 Aug 2015| |Beta8 | 21 Sep 2015| |RC1 | Nov 2015| |RC2 Pre1 | May 2016| ``` Will dig into this.

claunia commented

2026-01-29 14:20:12 +00:00

@xoofx commented on GitHub (Jun 19, 2016):

Should be fixed by commit 593bf08
Version 0.5.3 on the way to NuGet
Thanks for the report!

@xoofx commented on GitHub (Jun 19, 2016): Should be fixed by commit 593bf08 Version 0.5.3 on the way to NuGet Thanks for the report!

claunia commented

2026-01-29 14:20:16 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

Awesome. Thanks :)

@madskristensen commented on GitHub (Jun 19, 2016): Awesome. Thanks :)

claunia commented

2026-01-29 14:20:22 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

I can't get this to work. Now it won't render a table with or without missing | characters

@madskristensen commented on GitHub (Jun 19, 2016): I can't get this to work. Now it won't render a table with or without missing `|` characters

claunia commented

2026-01-29 14:20:24 +00:00

@xoofx commented on GitHub (Jun 19, 2016):

Could you reopen another bug with an isolated case?

@xoofx commented on GitHub (Jun 19, 2016): Could you reopen another bug with an isolated case?

claunia commented

2026-01-29 14:20:30 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

It's the exact same case. The following markdown is the only content in the file

|Milestone|Release Date|
|---------|------------|
|Beta7    | 24 Aug 2015|
|Beta8    | 21 Sep 2015|
|RC1      |    Nov 2015|
|RC2 Pre1 |    May 2016|

This is the rendered output:

<p>|Milestone|Release Date|
|&mdash;&mdash;&mdash;|&mdash;&mdash;&mdash;&mdash;|
|Beta7    | 24 Aug 2015|
|Beta8    | 21 Sep 2015|
|RC1      |    Nov 2015|
|RC2 Pre1 |    May 2016|</p>

Confirmed by babelmark3 as well

@madskristensen commented on GitHub (Jun 19, 2016): It's the exact same case. The following markdown is the only content in the file ``` markdown |Milestone|Release Date| |---------|------------| |Beta7 | 24 Aug 2015| |Beta8 | 21 Sep 2015| |RC1 | Nov 2015| |RC2 Pre1 | May 2016| ``` This is the rendered output: ``` html <p>|Milestone|Release Date| |———|————| |Beta7 | 24 Aug 2015| |Beta8 | 21 Sep 2015| |RC1 | Nov 2015| |RC2 Pre1 | May 2016|</p> ``` Confirmed by babelmark3 as well

claunia commented

2026-01-29 14:20:32 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

Well, according to babelmark3, Markdig (Extra) seems to render it correctly. What does the Extra refer to and how can I use it?

@madskristensen commented on GitHub (Jun 19, 2016): Well, according to babelmark3, _Markdig (Extra)_ seems to render it correctly. What does the _Extra_ refer to and how can I use it?

claunia commented

2026-01-29 14:20:36 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

This is my builder code:

var builder = new MarkdownPipelineBuilder()
    .UseEmojiAndSmiley()
    .UseSmartyPants()
    .UseAdvancedExtensions();

@madskristensen commented on GitHub (Jun 19, 2016): This is my builder code: ``` c# var builder = new MarkdownPipelineBuilder() .UseEmojiAndSmiley() .UseSmartyPants() .UseAdvancedExtensions(); ```

claunia commented

2026-01-29 14:20:41 +00:00

@madskristensen commented on GitHub (Jun 19, 2016):

Ok, I narrowed it down and will be opening a new bug

Issue #13

@madskristensen commented on GitHub (Jun 19, 2016): Ok, I narrowed it down and will be opening a new bug Issue #13

claunia referenced this issue

2026-01-29 14:28:42 +00:00

Add support for normalize - markdown document rountrip #147

claunia referenced this issue

2026-01-29 14:45:20 +00:00

[PR #32] [CLOSED] Add support for normalizing Markdown #770