Lines Matching refs:to
35 can [see the source for it by adding '.text' to the URL][src].
45 Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
50 Markdown's syntax has been influenced by several existing text-to-HTML
64 as to look like what they mean. E.g., asterisks around a word actually
73 Markdown's syntax is intended for one purpose: to be used as a
76 Markdown is not a replacement for HTML, or even close to it. Its
77 syntax is very small, corresponding only to a very small subset of
78 HTML tags. The idea is *not* to create a syntax that makes it easier
79 to insert HTML tags. In my opinion, HTML tags are already easy to
80 insert. The idea for Markdown is to make it easy to read, write, and
86 use HTML itself. There's no need to preface it or delimit it to
87 indicate that you're switching from Markdown to HTML; you just use
94 to add extra (unwanted) `<p>` tags around HTML block-level tags.
96 For example, to add an HTML table to a Markdown article:
115 you'd prefer to use HTML `<a>` or `<img>` tags instead of Markdown's
125 and `&`. Left angle brackets are used to start tags; ampersands are
126 used to denote HTML entities. If you want to use them as literal
130 Ampersands in particular are bedeviling for web writers. If you want to
131 write about 'AT&T', you need to write '`AT&T`'. You even need to
132 escape ampersands within URLs. Thus, if you want to link to:
136 you need to encode the URL as:
140 in your anchor tag `href` attribute. Needless to say, this is easy to
144 Markdown allows you to use these characters naturally, taking care of
149 So, if you want to include a copyright symbol in your article, you can write:
157 Markdown will translate it to:
167 Markdown will translate it to:
172 ampersands are *always* encoded automatically. This makes it easy to use
173 Markdown to write about HTML code. (As opposed to raw HTML, which is a
175 and `&` in your example code needs to be escaped.)
193 significantly from most other text-to-HTML formatters (including Movable
197 When you *do* want to insert a `<br />` break tag using Markdown, you
200 Yes, this takes a tad more effort to create a `<br />`, but a simplistic
226 corresponding to header levels 1-6. For example:
236 closing hashes don't even need to match the number of hashes
237 used to open the header. (The number of opening hashes
251 know how to create a blockquote in Markdown. It looks best if you hard
261 Markdown allows you to be lazy and only put the `>` before the first
278 > Back to the first level.
308 is equivalent to:
326 It's important to note that the actual numbers you use to mark the
348 you'd get the exact same HTML output. The point is, if you want to,
351 But if you want to be lazy, you don't have to.
358 up to three spaces. List markers must be followed by one or more spaces
369 But if you want to be lazy, you don't have to:
418 paragraphs, but here again, Markdown will allow you to be
424 only required to indent the first line. Lorem ipsum dolor
430 delimiters need to be indented:
438 to be indented *twice* -- 8 spaces or two tabs:
445 It's worth noting that it's possible to trigger an ordered list by
501 easy to include example HTML source code using Markdown -- just paste
518 it's also easy to use Markdown to write about Markdown's own syntax.
554 put the URL where you want the link to point, along with an *optional*
569 If you're referring to a local resource on the same server, you can
575 which you place a label of your choosing to identify the link:
579 You can optionally use a space to separate the sets of brackets:
591 indented from the left margin using up to three spaces);
605 single quotes from being used to delimit link titles.
612 or tabs for padding, which tends to look better with longer URLs:
614 [id]: http://example.com/longish/path/to/resource/here
629 The *implicit link name* shortcut allows you to omit the name of the
631 Just use an empty set of square brackets -- e.g., to link the word
632 "Google" to the google.com web site, you could simply write:
650 tend to put them immediately after each paragraph in which they're
686 The point of reference-style links is not that they're easier to
696 allowing you to move the markup-related metadata out of the paragraph,
727 the same character must be used to open and close an emphasis span.
766 one after the opening, one before the closing. This allows you to place
780 entities automatically, which makes it easy to include example HTML
793 to produce:
802 Admittedly, it's fairly difficult to devise a "natural" syntax for
805 Markdown uses an image syntax that is intended to resemble the syntax
810 
812 
819 * followed by a set of parentheses, containing the URL or path to
828 are defined using syntax identical to link references:
830 [id]: url/to/image "Optional title attribute"
833 dimensions of an image; if this is important to you, you can simply
844 … or email address with angle brackets. What this means is that if you want to show the actual text…
854 entity-encoding to help obscure your address from address-harvesting
866 which will render in a browser as a clickable link to "address@example.com".
877 Markdown allows you to use backslash escapes to generate literal
879 formatting syntax. For example, if you wanted to surround a word