Lines Matching refs:will
146 an HTML entity, it remains unchanged; otherwise it will be translated
153 and Markdown will leave it alone. But if you write:
157 Markdown will translate it to:
162 angle brackets as delimiters for HTML tags, Markdown will treat them as
167 Markdown will translate it to:
223 Any number of underlining `=`'s or `-`'s will work.
377 If list items are separated by blank lines, Markdown will wrap the
383 will turn into:
396 will turn into:
418 paragraphs, but here again, Markdown will allow you to be
471 Markdown will generate:
487 will turn into:
502 it and indent it, and Markdown will handle the hassle of encoding the
509 will turn into:
527 following lines will produce a horizontal rule:
672 Both of the above examples will produce the following HTML output:
704 emphasis. Text wrapped with one `*` or `_` will be wrapped with an
705 HTML `<em>` tag; double `*`'s or `_`'s will be wrapped with an HTML
716 will produce:
752 will produce:
761 which will produce this:
773 will produce:
781 tags. Markdown will turn this:
848 Markdown will turn this into:
853 Markdown will also perform a bit of randomized decimal and hex
855 spambots. For example, Markdown will turn this:
866 which will render in a browser as a clickable link to "address@example.com".
868 (This sort of entity-encoding trick will indeed fool many, if not
871 will probably eventually start receiving spam.)