mirror of
https://github.com/ilyakooo0/urbit.git
synced 2024-12-18 20:31:40 +03:00
47 lines
1.6 KiB
Plaintext
47 lines
1.6 KiB
Plaintext
/+ sqar
|
|
// /=try=/daun
|
|
!:
|
|
=-
|
|
;html
|
|
;head
|
|
;title: skuaring
|
|
==
|
|
;body
|
|
;p: 15 skwared is *{(sing (sqar -))}
|
|
==
|
|
==
|
|
'''
|
|
## Why is a spec needed?
|
|
|
|
John Gruber's [canonical description of Markdown's
|
|
syntax](http://daringfireball.net/projects/markdown/syntax)
|
|
does not specify the syntax unambiguously. Here are some examples of
|
|
questions it does not answer:
|
|
|
|
1. How much indentation is needed for a sublist? The spec says that
|
|
continuation paragraphs need to be indented four spaces, but is
|
|
not fully <emph>explicit</emph> about sublists. It is natural to think that
|
|
they, too, must be indented four spaces, but `Markdown.pl` does
|
|
not require that. This is hardly a "corner case," and divergences
|
|
between implementations on this issue often lead to surprises for
|
|
users in real documents. (See [this comment by John
|
|
Gruber](http://article.gmane.org/gmane.text.markdown.general/1997).)
|
|
|
|
2. Is a blank line needed before a block quote or header?
|
|
Most implementations do not require the blank line. However,
|
|
this can lead to unexpected results in hard-wrapped text, and
|
|
also to ambiguities in parsing (note that some implementations
|
|
put the header inside the blockquote, while others do not).
|
|
(John Gruber has also spoken [in favor of requiring the blank
|
|
lines](http://article.gmane.org/gmane.text.markdown.general/2146).)
|
|
|
|
3. Is a blank line needed before an indented code block?
|
|
(`Markdown.pl` requires it, but this is not mentioned in the
|
|
documentation, and some implementations do not require it.)
|
|
|
|
``` markdown
|
|
paragraph
|
|
code?
|
|
```
|
|
'''
|