Multi-line table entry or way to ignore line break. #321

New Issue

claunia · 2026-01-29T14:33:45Z

claunia commented

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

Originally created by @qqkookie on GitHub (Aug 13, 2019).

For example, table with three rows and two columns each.

 Header One  | Header Two   
 -------------- | -----------------------------
 Row1           | This is This is very, very very very very longooooooooo ooooooooooooooooo line. 
 Row2          | Short entry

I like to break "This is very very loooo...ng entry" into two source line.

 Header One  | Header Two   
 -------------- | -----------------------------
 Row1           | This is This is very, very very very very 
longooooooooo ooooooooooooooooo line. 
 Row2          | Short entry

This does not mean that it will break line in display (like <BR>) Just markdown parser will ignore newline after the last "very" and continue accept next line as part of the table entry. This is more consistent behavior for markdown format which largely treats single line break as space in source.
This can be done by adding "line continuation" back slash (\) as character escape or some other mean like enclosing the multi-line entry or whole the table itself with bracket ({{ entry... }}) or any similar way.

TRDR: There must be some way to accept long table entry spreaded in 2 lines as single table entry.

Originally created by @qqkookie on GitHub (Aug 13, 2019). For example, table with three rows and two columns each. ``` Header One | Header Two -------------- | ----------------------------- Row1 | This is This is very, very very very very longooooooooo ooooooooooooooooo line. Row2 | Short entry ``` I like to break "This is very very loooo...ng entry" into two source line. ``` Header One | Header Two -------------- | ----------------------------- Row1 | This is This is very, very very very very longooooooooo ooooooooooooooooo line. Row2 | Short entry ``` This does not mean that it will break line in display (like \<BR\>) Just markdown parser will ignore newline after the last "very" and continue accept next line as part of the table entry. This is more consistent behavior for markdown format which largely treats single line break as space in source. This can be done by adding "line continuation" back slash (\\) as character escape or some other mean like enclosing the multi-line entry or whole the table itself with bracket ({{ entry... }}) or any similar way. TRDR: There must be some way to accept long table entry spreaded in 2 lines as single table entry.

claunia added the enhancement wontfix labels 2026-01-29 14:33:45 +00:00

claunia closed this issue

2026-01-29 14:33:46 +00:00

claunia commented

2026-01-29 14:33:46 +00:00

@xoofx commented on GitHub (Oct 24, 2019):

afaik, none of the existing markdown parser table implementation support this, so we won't try to support this for now.

@xoofx commented on GitHub (Oct 24, 2019): afaik, none of the existing markdown parser table implementation support this, so we won't try to support this for now.

claunia commented

2026-01-29 14:33:46 +00:00

@schaveyt commented on GitHub (Oct 22, 2021):

@xoofx Please reconsider.

Pandoc does, indeed, have the multiline-table extension and its a god send. Without this pandoc feature, it is unlikely we would have been able to convince our technical writers to switch from MS Word to markdown/pandoc.

@schaveyt commented on GitHub (Oct 22, 2021): @xoofx Please reconsider. Pandoc does, indeed, have the [multiline-table extension](https://pandoc.org/MANUAL.html#extension-multiline_tables) and its a god send. Without this pandoc feature, it is unlikely we would have been able to convince our technical writers to switch from MS Word to markdown/pandoc.

claunia commented

2026-01-29 14:33:46 +00:00

@xoofx commented on GitHub (Oct 22, 2021):

I have no sparetime dedicated to implement new features for markdig and GitHub doesn't even support this. Folks that would start to author files with such a rule on GitHub would get something like this:

Header One	Header Two
Row1	This is This is very, very very very very
longooooooooo ooooooooooooooooo line.
Row2	Short entry

which is really not desirable. But anyway, PR welcome if someone has the courage to implement such a feature (it would have to be optional in that case).

@xoofx commented on GitHub (Oct 22, 2021): I have no sparetime dedicated to implement new features for markdig and GitHub doesn't even support this. Folks that would start to author files with such a rule on GitHub would get something like this: Header One | Header Two -------------- | ----------------------------- Row1 | This is This is very, very very very very longooooooooo ooooooooooooooooo line. Row2 | Short entry which is really not desirable. But anyway, PR welcome if someone has the courage to implement such a feature (it would have to be optional in that case).

claunia commented

2026-01-29 14:33:47 +00:00

@schaveyt commented on GitHub (Oct 22, 2021):

I don't understand. Correct, GitHub does not support this format and it would be considered an "additional extension". Is this what you are trying to say?

@schaveyt commented on GitHub (Oct 22, 2021): I don't understand. Correct, GitHub does not support this format and it would be considered an "additional extension". Is this what you are trying to say?

claunia referenced this issue

2026-01-29 14:47:38 +00:00

[PR #321] [CLOSED] Normalize and PlainText rendering #943

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/markdig#321