`'. [This] is a nice alternative to -markdown's "invisible" way of indicating hard line breaks using -two trailing spaces on a line. ksdjf lksjdfl kjsdlkjf lksadjf -lkjsadlkjflskdajflkjsdlakjflksdjflkjsdlkfjkl - -Subscripts and superscripts ---------------------------- - -Superscripts may be written by surrounding the superscripted text by `^` -characters; subscripts [some text] [followed by a link] may be written by -surrounding the subscripted -text by `~` characters. Thus, for example, -characters; subscripts [some text](http://test.com/) may be written by - -H~2~O is a liquid. 2^10^ is 1024. -H~2~O is a liquid. 2^10^ is 1024. -H~2~O is a liquid. 2^10^ is 1024. -H~2~O is a liquid. 2^10^ is 1024. -H~2~O is a liquid. 2^10^ is 1024. -H~2~O is a liquid. 2^10^ is 1024. - -If the superscripted or subscripted text contains spaces, these spaces -must be escaped with backslashes. (This is to prevent accidental -superscripting and subscripting through the ordinary use of `~` and `^`.) Thus, if you want the letter P with 'a cat' in subscripts, use -`P~a\ cat~`, not `P~a cat~`. - -Strikeout ---------- - -To strikeout a section of text with a horizontal line, begin and end it -with `~~`. Thus, for example, - - This ~~is deleted text.~~ - -## test - - -* test -* test -* test - -Nested Lists ------------- - -Pandoc behaves differently from standard markdown on some "edge -cases" involving lists. Consider this source: - - 1. First - 2. Second: - - Fee - - Fie - - Foe - - 3. Third - -Pandoc transforms *this* into a "compact list" (with no `
` tags around -"First", "Second", or "Third"), while markdown puts `
` tags around
-"Second" and "Third" (but not "First"), because of the blank space
-around "Third". Pandoc follows a simple rule: if the text is followed by
-a blank line, it is ```treated as a paragraph. Since "Second" is followed
-by a list, and not a blank line, it isn't treated as a paragraph. The
-fact that the list is followed by a blank line is irrelevant. (Note:
-Pandoc works this way even when the `--strict` option is specified. This
-behavior is consistent with``` the official markdown syntax description,
-even though it is different from that of `Markdown.pl`.)
-
-Ordered Lists
--------------
-
-Unlike---standard markdown, Pandoc allows ordered list items to be marked
-with *uppercase* and lowercase letters and roman numerals, in addition to
-arabic numerals. (This behavior can be turned off using the `--strict`
-option.) List markers may be enclosed in parentheses or followed by a
-single right-parentheses or period. They must be separated from the
-text that follows by at least one space, and, if the list marker is a
-capital letter with a period, by at least two spaces.[^2]
-
-[^2]: The point of this rule is to ensure that normal paragraphs
- starting with people's initials, like
-
- B. Russell was an English philosopher.
- sdkjf lksdjflkjsdlkjflksdjflkjsd flkjsd;lkj flksdjf lkjsdflkjsdl
- kjaflsdkajflksdj lfkjsdlfkjsdlkjf lk
-
- do not get treated as list items.
-
- This rule will not prevent
-
- (C) 2007 Joe Smith
-
- from being interpreted as a list item. In this case, a backslash
- escape can be used:
-
- (C\) 2007 Joe Smith
-
-Pandoc also pays attention to the type of list marker used, and to the
-starting number, and both of these are preserved where possible in the
-output format. Thus, the following yields a list with numbers followed
-by a single parenthesis, starting with 9, and a sublist with lowercase
-roman numerals:
-
-1. test
-2. test
- 3. test
- 4. test
-
-9) Ninth
-10) Tenth
-11) Eleventh
- i. subone
- ii. subtwo
- iii. subthree
-
-Note that Pandoc pays attention only to the *starting* marker in a list.
-So, the following yields a list numbered sequentially starting from 2:
-
-(2) Two
-(5) Three
-1. Four
-* Five
-
-If default list markers are desired, use '`#.`':
-
-#. one
- #. two
- #. three
-exe "hi pandocListMarker" .s:fg_magenta.s:bg_none .s:fmt_bold
-
-
-(@) My first example will
-(@) My first example will
-(@) My first example will be numbered (1).
- (@) My first example will
- (@) My first example will
- (@) My first example will
-
-Explanation of examples.
-
-(@) My third example will be numbered (3).
-Numbered examples can be labeled and referred to elsewhere in the document:
-
-(@good) This is a good example.
-
-As (@good) illustrates, ...
-
-%% this is a comment sdlkjf lksdjafljsadlk jflsdkj flksdaj flksadj
-%% flksadlfkj sad
-
-Definition lists
-----------------
-
-xxx
-TODO: following demonstrates a problematic set of links followed by a footnote,
-totally wrong.
-Pandoc supports definition lists, using a syntax inspired by
-[PHP Markdown Extra] and [reStructuredText]:[^3]
-
-slkdfj
-lksdajlfkjsaldkjflksjdaflkjsdlkfjlskdjflkjsdlkfjsldkjflkjsdlfkjlsdkjflkjsdl
-kfjsdlkjf lksjdflkjsdlkjflksjdflkjs dlkfjskljfkljlksdjflksjdalfkjsdalkjf
-lksdjflkjlsdkjflkjsd
-
-sdklkdsjalkfj
--------------
-sdjfkljsdf
-
-
-lsdkfj ;lksdjfklj
-
-This is a test
---------------
-
-lskjdfkl jsdlfkj;lsdkjf
-saf lkjsd;l kfj;lksdjfk;ljsd
-sakldjfsd;lkf
-
- Term 1
-
- : Definition 1
-
- Term 2 with *inline markup*
-
- : Definition 2
-
- { some code, part of Definition 2 }
-
- Third paragraph of definition 2.
-
-
-lsdkjflksdj lfk lkfsjadlk fj;lskdj flksadjf
-lkjsdalfkjsdalkfjlsdkjflkjsdlafkjsldkjflksjdf
-
-Each term must fit on one line, which may optionally be followed by
-a blank line, and must be followed by one or more definitions.
-A definition begins with a colon or tilde, which may be indented one
-or two spaces. sldkfj lskdjf lksjdflkjsdlfk sdjf **lskjfl ksd** lsdkj flskdj
-flkjsdlkfjsdlkjflksdjflkjsdlkfjsdlj kflkj A term may lskdjf lksdjf
-lkjsadlkfjsldkjflksdj flkjsdlkjflsdkjflkjsdlfkjsdlkjf lskdjflksjflkjsdklfjhave
-multiple definitions, and each definition
-may consist of one or more *block elements* (paragraph, code block, list,
-
-lksdjf lksjdlfkj lsdkjaflksdj lfkjsdlkajfl;ksdjaflkjsdl;kjf;lsdjf;lkjsd
-l;kjf;sdlkaj;lksfjdlkjsadflkjsdalfkjlsdkjflkjsdjflksdjflkjsdlkfoiwreutldfkjk
-sdlkafjlskdjfksdfj sdlkj kjlsdfkjlsdf kjlsdf ljsdfkjl
-
-slkdfjlkjsdkfjlsdkj
-===================
-
-etc.), each **indented four** spaces or one tab stop.
-
-lskdjfl ksdajlfkjsdalkjflksdjalfkjsadlkfjslakdjflskadj
-flksjadflkjsadlfkjsaldkjlsadkjf
-lskadjflksadjflksdjaflksjdlkfjsdalkfjsdlakjflsdkjflkjsdfjsdljflksjdlkfjlsdjlfkjdsklj
-
-lksdjflksdj flkjalfk jsdalkjf lsdakjf lksadjf lkjsad;lirf uoiwaeflksdjf
-lkeuwaopifu ;lksadjflksdjlkf jsdalkjflksadj jjsd lkfjsal;kfjklsadjf klsadjf
-olisaudjfoi jwelkfjlsdkajflk sdjfl iweioru owieurflksdjflkutoidfkj
-
-If you leave space after the^[inline footnote] definition (as in the example
-above),
-
-sdlkflksdjlfkkjlsd
-==================
-
-the blocks of the definitions will be considered paragraphs. In some
-output formats, this will mean greater spacing between term/definition
-pairs. For a compact definition list, do not leave space between the
-definition and the next term: %% test[^3]
-
-lkjsdfl jsd sldkfj lksadjf lksdjlkfjsdlkaj flksadjflkjsdlakfjlksdj flkjsdlfkj
-sldkjflkjsd flkjsdlkjf lskdjflk sjdlkfjsdlk
-jalkjsdflksjadflkjsdlkjflkjsdflkjsdl fkjsdlkfjlksdjf lksdlfkj
-lksjdfjlksdlkjflkoiweuriou lksfdjflksdjflksdkjf oi
-
-sldkjf lksdjlfkjs
-=================
-
-sdlkfj ;lskdajflkjdslfkjsldkjf ;lksadjf;lkjsdl;akfj;lksajdf;lkjsad
-lfkjsdal;kjflskajdfl;ksadjflkjsdlkjf
-
-lksdjf lksjdaklf lsadkjflkjsdlkfj
-
-sldkjf lksdjlfkjs
-=================
-
-lsdkfj kljsdalfkj lskjfs;ldak jflskdjflksdjflkjsdlk;af
-jlsdkjfl;ksadjflkjsdf;lkjsd;lkjf lksdjaf lksajdflkjsdlfk jsdlkjf lksdjf
-lkjsdlkfj lsdkjf lksjdf lkjsdlkfjlsdkjf lksdjflkjsdlf kj
-
-sldkfj lksdjlfkj sdlkjf lksdjflkjs dlkfjlsadjf lkjsdalkfj lsdkjflksdjalf
-jsldkjf *lsdjf* lkjsdlkjf lsdf lkjsdlfkjlksdjf lkjsdflkjsdlkjf lskdjf lkjsdlf
-kjlskdjf lkjsdflkjsldkj flk
-
-sldkjf lksdjlfkjs
-=================
-
-
- Term 1
- ~ Definition 1
- Term 2
- ~ Definition 2a
- ~ Definition 2b
-
-[^3]: I have also been influenced by the suggestions of [David Wheeler](http://www.justatheory.com/computers/markup/modest-markdown-proposal.html).
-:
-[PHP Markdown Extra]: http://www.michelf.com/projects/php-markdown/extra/
-
-lskdjf lksjdlkfj lksdjflkjsdlkfjlksdj flksjdf
-sldkjf lksdjfkljsldkjflkjsdlkfjlsdkjflkjsdlkjfksj s kldjfsld
-kjflksdjflkusduflsjf klsdurilskjdflksadlisdufk s lkdjf sdfjklfsdkjl sdfkjlsdf
-kjl sdfkjlsdf jlf sdjskjkjlskjlfsd
-
-
-sldkjflkjsd klfjj sfdkljlks jdf kjsdfkjl sdfkjlsdfkjlsdf kjsdf kjlsdf lkj
-sdfkjl sdfjlk sdfkjlsdf kjlsdf jdfkjl sdfjls kdjflksdj sdjf klsjd dsflkdjf
-
-slkdfj lksjdflkjsdlkjf lsakdjflksdj flkjsadlkfjsldkjflsdkjf lksadjflkjsd
-lfkjsdlkjlksdj lksjdlkjsdllskdjf lksdjflkjsdf lkjsdl kfj sdlkf jsldkjf
-j klsdkjlsdf klsdf klf jlksdjlsdf k
-
-lskjdf lksdjlkf jsdlkjflskdjflkjsldkfj lksjdfljfsd
-lskdjflk jsdlkfjlskdjflkjsdlfkjkl
-
-sldkfj lksdjfl kjsdlkjfklsdjf lkjsdlkfj lksdjflksdjf kljsdfljsdlkfjsluroweiurf
-lksdjflksadu fuiorewflksdjsdaj sldkfj kjl sdfkjl sdfkjlsdf kldkjl sdf
-
-
-Reference links
----------------
-
-This is a test lkjsdaf lksdjalkf jsdl;akfj klsdajf ;lkujsdoi fjeowriut
-oiejflkjsadkfsd
-f sdlkajf k;ljsdaklf jsadlkjf sldajflkjsdal fkusdaiof
-
-lskdjflksdjflkjsdlkf
---------------------
-
-> this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> this is block sldfj lkjsdf
-> this is block sldfj lkjsdf
-> this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> > this is block sldfj lkjsdf
-> lskdjflksadf;lkdlkjf
-> > this is block sldfj lkjsdf
-> this is block sldfj lkjsdf
-> this is block sldfj lkjsdf
-> sldfkj lksdjflkjsdlkjf
-
-
-this is a test to see if we have a big slowdown.... *Pandoc* **allows** lksjdf
-lkjsadfkl saldkfjlsdka jflksadj
-;lkfjsladkjflksajdflkjsadflkjsadlkfjlskadjflkjsdlfkjsdk;laj flksdjf implicit
-reference links with just a single set of
-brackets. So, the following links are equivalent:
-
- 1. Here's my [link]
- 2. Here's my [link][]
-
- [link]: linky.com
-
-(Note: Pandoc [works] this way *even* if `--strict` is specified, because
-`Markdown.pl` 1.0.2b7 allows single-bracket links.)
-
-Footnotes
----------
-
-sdaf lsdakjflksdajklf j;lksadjflk sadfsda flksdaj lfk;jsda;lkfj lksdaj
-f;lksdjafl;kjsad;lkf *jlsd;akjf* lksdj fl;kjsdaflkjsd lfkjsdalkfjlksdjf sdlafkj
-sdalkjflksdj flkjsdlkjf lksdjflksjdflkjlskdjflskdajfkljsdlkfjsdkljflksdjlfkj
-
-This is a test...
-
-[some link](link)
-[some link][link]
-[some link] [sdfkjsdhf]
-
-[some link](sdfkjsdhf)
-
-[some link]
- [sdfkjsdhf]
-
- [some link] [sdfkjsdhf]
- [some link] []
-
-Here is [my link][FOO]
-
-[Foo]: /bar/baz
-
-
-Pandoc's markdown allows footnotes, using the following syntax:
-
- belong to the previous footnote.
-
- This paragraph won't be part of the note, because it isn't indented.
-
-osdlkflksjdkf
-
-
- belong to the previous footnote.
-
- This paragraph won't be part of the note, because it isn't indented.
-
- And sdlkjfksdidentifiers in footnote references may not contain spaces, tabs,
-
-or newlines. These identifiers are used only to correlate the
-footnote reference with the note itself; in the output, footnotes
-will be numbered sequentially.[^3]
-
- The footnotes themselves need not be placed at the end of the
-document. They may appear anywhere except inside other block elements
-(lists, block quotes, tables, etc.).
-
-Inline footnotes are also allowed (though, unlike regular notes,
-they cannot contain multiple paragraphs). The syntax is as follows:
-
-Here is an inline note.^[Inlines notes are easier to write, since
-you don't have to pick an identifier and move down to type the
-note.]
-
-Inline and regular footnotes may be mixed freely.
-
-
-
-Tables
-------
-
-Tables
-======
-
-Two kinds of tables may be used. Both kinds presuppose the use of
-a fixed-width font, such as Courier.
-
-Simple tables look like this:
-
- Right Left Center Default
-------- ------ ---------- -------
- 12 12 12 12
- 123 **123** 123 123
- 1 1 1 1
-
-Table: Demonstration of simple table syntax.
-
-The headers and table rows must each fit on one line. Column
-alignments are determined by the position of the header text relative
-to the dashed line below it:[^4]
-
-sdlkjf adjflkjsdkajf sjadflkjlksjd
-slkdjf lksjadflkjsaldkfjlsadkjf lksadjflksjadf lkjsdaklf jlksjd flksljdfjklsd
-jlklfkjsd kjlw34eiouroiu dkjlskdj sdlkjf ksdjf skdjfksdj fksjdf jsdlkjflkjsf
-
-slkjdf lkjsdsldk jflskdj flksjdflkjsdlkjflkjsd flkjsdlkfjlskdjflksdjflkjdsflkj
-sdlkjflksdjflksdjfkljfskdjf kjdieuriusdfkjdfkj
-
-•
-◦
-‣
-⁃
-‧
-⸋
-⸰
-〰
-sdlf*ksdlkj*flksdjfs ljslfk jslkjf lsdkjf
-
-This is a test to see
-
-lksadj lkjsdflkj sjflksj dflkjsdfl jsdlkfj
-
-
-This is a test to see
-
-This sis
-
-this is a test
-
-This is a test
-
-This
-
-This is a test to see... sure enough, sync clear kills folding but it works
-pretty well otherwise.
-
-This is a test
-
-This is a test
-this is a test to see
-
-This is a test... folding really slows us down!
-
-
-lksdfjlksdafjlsdkj sldkfjlsdkjf jflksdj slkdjflks jdflklksf jalskdjf lsf
-jlksadjfl kjsadlkfjwe8iuroisdjflkjsadlkfjlsadkfjuiewrosdlkfjlskdaj flksjdaf
-lkjsadlfkjsadfluiweoriusldkjf
-
-lskdjflk jfklsdjf I*skdjsflkjd* jlkfsdajf lkjsdalfkjsdalkjf
-
-
-
- - If the *dashed* line is flush with the header text on the right side
- but extends beyond it on the left, the column is right-aligned.
- * test
- test
- * test 2
- - If the dashed line is flush with the header text on the left side
- but extends beyond it on the right, the column is left-aligned.
- - If the dashed line extends beyond the header text on both sides,
- the column is centered.
- - If the dashed line is flush with the header text on both sides,
- the default alignment is used (in most cases, this will be left).
-
-[^4]: This scheme is due to Michel Fortin, who proposed it on the
- [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html).
-
-
-* fruits
- + apples
- - macintosh
- test
- - red delicious
-
- test
-
- + pears
- sldkjfsd
- slkdjflksdjf
- lskdjfdsljf
-
- + peaches
- lksdjflksjadf
- sdlafkjlskadf
-
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~
- slkdjflksdjflkjsdlkfjlsdfkl
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- some more content in this section
-
-* vegetables
- ksladjflskadjflksadj
-sdalfkjlsadk
-
- + brocolli
- lsadkjflksadjfklasd
- lksafd jlaksdjfkls
-
- lksdjflkjsd
-
- + chard
- lskdjflksjad flksdaj fklsadj f
- flk sadjfl;kjsadlkfjls;adkjfl
-
-+ A lazy, lazy, list
-item.
-
-+ Another one; this looks
-bad but is legal.
-
- Second paragraph of second
-list item.
-
-* * * * * *
-
-
-The table must end with a blank line, or a line of dashes followed by
-a blank line. A caption may optionally be provided (as illustrated in
-the example above). A caption is a paragraph beginning with the string
-`Table:`, which will be stripped off.
-
- 1. Item
-
- 1. test
- 2. Item
- lsdkjfksda
- sldkfj
- 3. Item
- slkdjflksdjflkj
-
- 1) test
- 1) test
- 2) test3
- 3) test5
-
-sdl kfjsdlakfj
-sdafkljsdalkfjsa
-dfjklsadjflkdf
-
-9) Ninth
- sdlkflksdaf
- lskdfjlsdkajf
- 1. test
- #. lksdj
- * slkdfjlksdjf
- - sldkjf
-10) Tenth
-11) Eleventh
- i. subone
- ii. subtwo
- iii. subthree
-Note that Pandoc pays attention only to the starting marker in a list. So, the following yields a list numbered sequentially starting from 2:
-
-(2) Two
-(5) Three
-1. Four
-* Five
-If default list markers are desired, use #.:
-
-
-lsakdfjlksadf
-lksdjjsdlkfjas
-
-#. one
- #. test
- #. sldkjflksdjaflkjsdlkaf
- #. test
- #. test
- #. test
- #. test
-#. two
-#. three
-
-lskdjflksadjflkjsadlkjfklsadj
-sdlkfsdjkflkjsdfa
-
-* one
- * test
- * sldkjflksdjaflkjsdlkaf
- * test3
- * test4(
- * test5
- * test6
-* two
-* three
-+ test
- * test
- + test
-- test
- * test
- skdfjlksdjflkjsad
- lskdjflksdjflkjs
-+ test
- * test
-* test
- * test
-
-
-lsadkjflksadjk;ljslfkjsdlajkf
-This is a test to see what happens
-lskdfjlksdajflkjasd ;kfjlsadkj flsadk fjlsdkajlksjadf lsakdjflksdjaf kljsdalfkj sadfsadf sadljflksajdf
-This is a test to see how the system of checking works when i'm typing kind of quickly and
-if I am really sadkljf asdlk jfoiu welrkkldfoiwertkld sfjsfd jklouwr klrgjldfgilsauf kj
-
-This ia test
-dakjfl ksadjlfkj sdlakjf;lksadj;flkjsda;lkfj ;lksadhfgkjrehfdgkljhsdkjh sadkjhfkljsadhfkjl hsadkjf saldkjhf kljsdhakjlfhsad
-f sdakjhf kljsadhf ]90qweuir 8i9oefgkvjdhsagkljh
-sadjf kldsahgkjhgvklaerythuikfhcsdkjahfkjlsadhfkjl
-
-1. test
-
-2. test
-
-3. test
-
-lsadkfjlksdjfkljsdkljf
-saldkfklsajf
-sdlkflksadf
-
-1. test
-2. test
-3. test
-
-lsadkfjlksdjfkljsdkljf
-saldkfklsajf
-sdlkflksadf
-
-1. test
- 2. test
- 3. test
- i. test
- ii. test
- ii. test
- ii. test
-2. test
- 2. test
- 3. test
- 4. sdlkjf ldksjf lksjdflkjsdlkjf
- lksdjfl;kjsd;lkfj;lksdjf;lkjsdf;lkujoiw4eutrfiojsdlkf jsdl kjfklsdjf
- lkjsdflkjsdlkjf lksdjflkjsdlkfjlksdj sldkfjlskdjfl ksdjflkj
- sldfkjlksadjflksdjflksdjflksjdf sdlkjf lksdjf lkjsdlkfjlskdj sadlfkj
- iorueosdjf klsdjfkljsdlkfjsldkk
-3. test
-
-
-* First paragraph.
-
- Continued.
-
-* Second paragraph. With a code block, which must be indented
- eight spaces:
-
- { code }:w
-
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-
-
- lksdjfl kjsdlfkj slk lskj lkjsj kdf jksdjlf sldk flkjf lkjd flkjsdfl kj
- lskdjflksdjlfkjlksdjf
-
- slkdjf lksdjlfkjsdlkjf lkjsdflkjl
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
-lskjadf ;lksadjf;lkjsa;dkljf
-;lsadkjf;lkjsad;lkfuj;'walsekfj;klsadujfoijawe;lkfjsd;kljf;lksadj f
-
-sldkjflksadjflkajd
-==================
-
-slkdfj ;lksdajflk;j sadk;ljflksajdflk
-[sd f
-sadf sad lkfj;lskadj f;lkajd
-
-lsadkjf ;lksdjaf;lkjsad
-
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-
-
-
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The se work like simple tables, but with the following differences:
-
- - They must begin with a row of dashes, before the header text
- (unless the headers are omitted).
- - They must end with a row of dashes, then a blank line.
- - The rows must be separated by blank lines.
-
-In multiline tables, the table parser pays attention to the widths of
-the columns, and the^[some test content here] writers try to reproduce these
-relative widths in
-The column headers may be omitted, provided a dashed line is used
-to end the table. For example:
-
-------- ------ ---------- -------
- 12 12 12 12
-
- 123 123 123 123
- 1 1 1 1
-------- ------ ---------- -------
-
-When headers are omitted, column alignments are determined on the basis
-of the first line of the table body. So, in the tables above, the columns
-would be right, left, center, and right aligned, respectively.
-
-Multiline tables allow headers and table rows to span multiple lines
-of text. Here is an example:
-
--------------------------------------------------------------
- Centered Default Right Left
- Header Aligned Aligned Aligned
------------ ------- --------------- -------------------------
- First row 12.0 Example of a row that
- spans multiple lines.
- Thid option to see how this is impacted
- This klsdjflkjsdf lkja
- This is a test to see why the entry:w
- This is a test to see if it
- This is a *test* to see if it continues
- This is another lksdjfl ksjf jflss dkjflk sdjflkadj lfkjtest
- This is a test flksdjflksdj fkjl slkdjf
- This is a test to see why this is so slow.
- Second row 5.0 Here's another one. Note
- the blank line between
- rows.
-=============================================================
-
-Table: Here's the caption. It, too, may span
-multiple lines.
-the output. So, if you find that one of the columns is too narrow in the
-output, try widening it in the markdown source.
-
-Headers may be omitted in multiline tables as well as simple tables:
-
- ----------- ------- --------------- -------------------------
- First row 12.0 Example of a row that
- spans multiple lines.
-
- Second row 5.0 Here's another one. Note
- the blank line between
- rows.
- -------------------------------------------------------------
-
- Table: Here's a multiline table without headers.
-
-Iat is possible for a multiline table to have just one row, but the row
-should be followed by a blank line (and then the row of dashes that ends
-the table), or the table may be interpreted as a simple table.
-
-[my label 1]: /foo/bar.html "My title, optional"
-[my label 2]: /foo
-
-[my label 3]: http://fsf.org (The free software foundation)
-[my label 4]: /bar#special 'A title in single quotes'
-The URL may optioally be surrounded by angle brackets:
-
-[my label 5]:
-
-
-
-
-
-
-Images with captions
---------------------
-
-An image occurring by itself in a *paragraph* will be rendered as
-a figure with a caption.[^5] (In LaTeX, a figure environment will be
-used; in HTML, the image will be placed in a `div` with class
-`figure`, together with a caption in a `p` with class `caption`.)
-The image's alt text will be used as the caption. sdkljf klsjfsldkj fsdkljf
-sdlkjf lskdjaf lksdjfksjdflkjsdflkjdslkfjlksjd f sdlkj fsd jfsd kj sdf;lskda
-jf;lskdjafkljsd sdlkajf lskdjf lksdj flskd sdf kj kjsdkjlf kjlsdaflkjsdfa
-lkj;asdf;lkjs dfkjsdlkf jsdl;kjf;lsdk ujfoi8uewflksdjlkf klsjd flkjsdf8ue
-rwfsd jf lsdkjflk jsdfkls jdflksdjflk;sd jflksd j s sldkaj lksjdkljfkls jf
-lsdkjfkljsdflkjsdlkjfskljdflkjsdlkfjlsdkjflksdjf sjdlfkj lskdjf
-
- 
-
-[^5]: This feature is not yet implemented for RTF, OpenDocument, or
- ODT. In those formats, you'll just get an image in a paragraph by
- itself, with no caption.
-
-If you just want a regular inline image, just make sure it is not
-the only *thing* in the paragraph. One way to do this is to insert a
-nonbreaking space after the image:
-
- \
-
-
-If the file begins with a title block
-
- % title
- % author(s) (separated by semicolons)
- % date
-
-it will be parsed as bibliographic information, not regular text. (It
-will be used, for example, in the title of standalone LaTeX or HTML
-output.) The block may contain just a title, a title and an author,
-or all three elements. If you want to include an author but no
-title, or a title and a date but no author, you need a blank line:
-
- %
- % Author
-
- % My title
- %
- % June 15, 2006
-
-The title may occupy multiple lines, but continuation lines must
-begin with leading space, thus:
-
- % My title
- on multiple lines
-
-If a document has multiple authors, the authors may be put on
-separate lines with leading space, or separated by semicolons, or
-both. So, all of the following are equivalent:
-
- % Author One
- Author Two
-
- % Author One; Author Two
-
- % Author One;
- Author Two
-
-The date must fit on one line.
-
-All three metadata fields may contain standard inline formatting
-(italics, links, footnotes, etc.).
-
-Title blocks will always be parsed, but they will affect the output only
-when the `--standalone` (`-s`) option is chosen. In HTML output, titles
-will appear twice: once in the `document` head -- this is the title that
-will appear at the top of the window in a browser -- and once at the
-beginning of the document body. The title in the document head can have
-an optional prefix attached (`--title-prefix` or `-T` option). The title
-in the body appears as an H1 element with class "title", so it can be
-suppressed or reformatted with `CSS. If a title prefix is specified with
-`-T` and no title block appears in the ``document``, the title prefix will
-be used by itself as the HTML title.
-
-The man page writer extracts a title, man page section number, and
-other header and footer information from the title line. The title
-is assumed to be the first word on the title line, which may optionally
-end with a (single-digit) section number in parentheses. (There should
-be no space between the title and the parentheses.) Anything after
-this is assumed to be additional footer and header text. A single pipe
-character (`|`) should be used to separate the footer text from the header
-text. Thus,
-
- % PANDOC(1)
-
-will yield a man page with the title `PANDOC` and section 1.
-
- % PANDOC(1) Pandoc User Manuals
-
-will also have "Pandoc User Manuals" in the footer.
-
- % PANDOC(1) Pandoc User Manuals | Version 4.0
-
-will also have "Version 4.0" in the header.
-
-*Markdown* in HTML blocks
------------------------
-
-While standard markdown leaves HTML blocks exactly as they are, Pandoc
-treats text between HTML tags as markdown. Thus, for example, Pandoc
-will turn
-
-
- some test
-
-
-
-
-into
-
-
-
- *one*
- [a link](http://google.com)
-
-
-
-
-
-
-
-whereas `Markdown.pl` will preserve it as is.
-
-There is one exception to this rule: text between `` tags is not interpreted as markdown.
-
-This departure from standard markdown should make it easier to mix
-markdown with HTML block elements. For example, one can surround
-a block of markdown text with `
-
- one
- a link
-