![]() ![]() This 3SP table is spaced to look great in a fixed width font: pickle typical ingredients culture heat The same 3SP table without attempts to align: pickle typical ingredients culture heat The same GFM table without attempts to align: pickle | typical ingredients | culture | heat Kimchi | fermented cabbage, seasonings | Korea | 8Ĭornichons | gherkins, vinegar, tarragon | France | 0Īvakaya | mango, mustard seeds, oil, seasonings | India | 10 In this regard, behavior under changing font styles, I don’t think 3SP is much worse or better than a GFM table similarly aligned when entered: pickle | typical ingredients | culture | heat When I entered the 3SP table above, all of the columns were aligned in the variable-width font of the reply box:ģSP, variable-width aligned 1184×294 67.7 KB Kimchi fermented cabbage, seasonings Korea 8Ĭornichons gherkins, vinegar, tarragon France 0Īvakaya mango, mustard seeds, oil, seasonings India 10 If one is liberal with spaces, you can usually avoid visual ambiguity even if the table looks ragged, but worst case it can end up hard for a human to read. A problem would only occur when later editing the same table in some other context that uses a font with very different relative widths and spacing. Your idea, “Three Space Table” (3SP) if you don’t mind my giving it a name, works with variable width fonts and even narrow spaces at table creation time since one could use as many spaces as needed for visual clarity. Many variable fonts have repeated spaces at about half the width of a normal character, so it is possible to muck it up. ![]() I humbly asks for your considered opinions, Complex tables are for embedded HTML this only handles simple tables.Formatting does not cross columns: “* Col1 Col2*” is just be two asterisks.Do people want to allow cells like “Nasty 1”?.Writing the markdown in variable width fonts still works: it just takes a lot of extra spaces.Each entry, or ‘cell’, may have formatting within it, e.g., bold or emphasize or even sup/sub if supported. Everything is put in a TABLE tag, with one THEAD, TR, or TFOOT per line, and each entry is rendered into a TD. If this line is the second line, it designates a header line,and if the second from the bottom and not the second line, it designates a footer.A line with only dashes or equal signs designates a header or footer.We can add a rule for headers and footers as well: So this is not a table: Orcs 1,234 Nasty Buggers There are columns of spaces at least three wide down the entire table.It is it own paragraph of two or more lines.When I want I table in text, I type it: Orcs 1,234 Nasty buggers Similarly, naturally communicating in raw text will lead to headings and lists. Someone who never used Markdown might stumble onto emphasized, bold, and underline just by typing things. The original goal of Markdown is to create a rendering for the way people type normally. ![]() If there is a better format, please let me know. First, I’m new to working on CommonMark, so I’m guessing this is the best way to propose a new and consider nuances before writing code and submitting pull requests. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |