From be19ec302584732eca18de162a7eaf5d8649379e Mon Sep 17 00:00:00 2001 From: John MacFarlane Date: Sat, 24 Jan 2015 21:10:11 -0800 Subject: Removed spec-specific files (DTD, spec generation tools). --- alternative-html-blocks.txt | 247 -------------------------------------------- 1 file changed, 247 deletions(-) delete mode 100644 alternative-html-blocks.txt (limited to 'alternative-html-blocks.txt') diff --git a/alternative-html-blocks.txt b/alternative-html-blocks.txt deleted file mode 100644 index 3ba0d15..0000000 --- a/alternative-html-blocks.txt +++ /dev/null @@ -1,247 +0,0 @@ -# Appendix B: An alternate spec for HTML blocks {-} - -(The following spec departs less from original markdown than the -one described above, but is also less flexible.) - -An [HTML block](#html-block) begins -with an [open tag](#open-tag), [HTML comment](#html-comment), -[processing instruction](#processing-instruction), -[declaration](#declaration), or [CDATA section](#cdata-section). -This opening element may optionally be preceded by 1-3 spaces, -and must not be followed on a line by anything other than white space. - -If the opening tag is self-closing, or if it is an [HTML -comment](#html-comment), [processing -instruction](#processing-instruction), [declaration](#declaration), or -[CDATA section](#cdata-section), then the [HTML block](#html-block) -contains just that tag. - -If it is an [open tag](#open-tag), then the [HTML block](#html-block) -continues until a matching closing tag is found, or until the end -of the document. Note that the matching closing tag is not necessarily -the first closing tag of the same type that is encountered, since -that tag may close a later open tag of the same type. Open and closing -tags must be balanced. - -The contents of the HTML block are interpreted as raw HTML, and will not -be escaped in HTML output. - -Some simple examples: - -. - - - - -
- hi -
- -okay. -. - - - - -
- hi -
-

okay.

-. - - -. -
- -
- -

fooö

- -
- -
-. -
- -
- -

fooö

- -
- -
-. - -A self-closing tag: - -. -
-. -
-. - -Here we have an unclosed tag, and the block continues to the end of -the document: - -. -
-
-foo -
- -*bar* -. -
-
-foo -
- -*bar* -. - -A comment: - -. - -. - -. - -A processing instruction: - -. - -. - -. - -CDATA: - -. - -. - -. - -The opening tag can be indented 1-3 spaces, but not 4: - -. - - -. - -
<!-- foo -->
-
-. - -The opening tag must be on a line (or lines) by itself: - -. -
-foo -
-. -

foo

-. - -. -bar -. -

bar

-. - -The opening tag need not be an HTML block tag or even an HTML tag: - -. -
-foo - -. - -foo - -. - -. - -bar - -. - -bar - -. - -So, note the difference: - -. - -bar - - -bar -. - -bar - -

bar

-. - -This rule differs from John Gruber's original markdown syntax -specification, which says: - -> The only restrictions are that block-level HTML elements — -> e.g. `
`, ``, `
`, `

`, etc. — must be separated from -> surrounding content by blank lines, and the start and end tags of the -> block should not be indented with tabs or spaces. - -In some ways Gruber's rule is more restrictive than the one given -here: - -- It requires that an HTML block be preceded and followed by a blank line. -- It does not allow the start tag to be indented. -- It does not allow the end tag to be indented. -- It does not require that the open tag be an HTML block-level tag. - -Indeed, most markdown implementations, including some of Gruber's -own perl implementations, do not impose these restrictions. - -However, unlike Gruber's rule, this one requires that the open -tag be on a line by itself. It also differs from most markdown -implementations in how it handles the case where there is no matching -closing tag (a case not mentioned in Gruber's rule). In such a case, -the rule stated above includes the whole rest of the document in the -HTML block. - -- cgit v1.2.3