![]() ![]() And as before, it falls back to a valid table in existing GitHub-Flavored Markdown. These additional pipes and dashes make it look more table-like. Any new directions that ditch the original philosophy are fine, but they shouldn’t be called Mark down.įor better readability, the table could be written as follows: | The Title | The Name | The Phone | I think it important that the philosophy and spirit stay in the forefront of everyone’s minds as we try to get to v1.0 as well to v1.1 or v2. I realize, John, that you’ve already done this in What Is Markdown? Maybe just post and pin that at the top of the forum? Maybe create a topic titled “The Philosophy and Spirit of Markdown” or “The Markdown Prime Directive”, and pin it to the top of the forum? what do you think? I’d be happy to make the initial post (I’ve been drafting something about this), though it might be best if it came from John. It’s worth reading the discussion in that thread.Įven though it’s spelled out both by Gruber when he introduced Markdown and by in the introduction to CommonMark, a lot of ideas and proposals on this forum lose sight of it, and it confuses efforts to solidify and advance this standard. | Caption Text This syntax violates the Prime Directive. The earlier version was as follows: |=| | | | | | In this table, the Markdown text can be compressed to remove extra dashes, equals signs, and whitespace, as long as there remains whitespace next to colons |: :| for alignment and next to dots |.| for cell continuation.ĮDIT: I have revised the above syntax proposal to simplify it. Per-cell text alignment is indicated if a cell (or, in a multiline cell, the first line) starts and/or ends with a colon that is whitespace-separated from the cell’s text content. | Visually, the dots in each column resemble a vertical ellipsis which indicates that the above cell continues downward. Multi-line cell continuation is represented by row(s) whose cells each start and end with a single dot that is whitespace-separated from the cell’s text content. In the “delimiter row”, if the first cell contains only equals signs =, it indicates that the cells in the first column represent row headers.Ī row span is represented by cells containing only a carat/circumflex ^.Ī column span is represented by cells containing only a “less-than” symbol for column spans.)Ī caption is represented by text in the top-left cell (above all other cells, headers, etc.) ![]() ![]() ![]() Cells below that row represent other table cells. Cells above this row represent headers and subheaders. One row in the rendered table consists of cells containing only dashes - and cells containing only equals signs =. Rendered-gfm-table-revised.png 1712×762 60 KB text.|Ī future extension could implement this syntax.įor now, in GFM and other existing Markdown flavors, it falls back to an ordinary table whose cells contain symbols that visually represent the additional features: | Row Header 4 | Row | Each cell |: Centered :| Right-aligned :|: Left-aligned | | Row Header 2 | ^ | < | < | Rowspan only | Cell | | Row Header 1 | 3row, 3col span | < | < | Colspan only | < | | | Subheader 1 | Subheader 2.1 | Subheader 2.2 | Subheader 3.1 | Subheader 3.2 | | | Header 1 | Header 2 | < | Header 3 | < | Per-cell alignment using colon(s) : inside a cell, to the left/right/both of the cell’s first line of text (inspired by the |:-:| syntax for per-column alignment)Īn alternative syntax, for better compatibility with existing pipe tables: | Caption Text | | | | | | Multi-line cell continuation using a colon : in place of a pipe | (like in PostreSQL’s interactive terminal, as discussed by David Wheeler in RFC: A Simple Markdown Table Format and suggested above by illionas) Row spans using a carat/circumflex ^ (Thank you jgm)Ĭolumn spans using multiple pipes ||| ( MultiMarkdown, Maruku)Ĭaption surrounded by brackets on the line just below the table ( MultiMarkdown) Row headers, which are indicated by replacing dashes - with equals signs = in the first column’s delimiter row (Thank you again vas) Multiple rows of headers and subheaders (Thank you vas) ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |