+
+ mypic.jpg becomes 
+
+Requires Python-Markdown 1.6+
+'''
+
+import simplewiki.settings as settings
+import markdown
+
+class ImageExtension(markdown.Extension):
+ def __init__(self, configs):
+ for key, value in configs :
+ self.setConfig(key, value)
+
+ def add_inline(self, md, name, klass, re):
+ pattern = klass(re)
+ pattern.md = md
+ pattern.ext = self
+ md.inlinePatterns.add(name, pattern, "http://www.metacafe.com/watch/yt-tZMsrrQCnx8/pycon_2008_django_sprint_room/
' +>>> s = "`http://www.metacafe.com/watch/yt-tZMsrrQCnx8/pycon_2008_django_sprint_room/`" +>>> markdown.markdown(s, ['video']) +u'http://www.metacafe.com/watch/yt-tZMsrrQCnx8/pycon_2008_django_sprint_room/
{% block wiki_page_title %}{% endblock %}
++ +{% block wiki_panel %} + +
+
+
+
+{% endblock %}
+
+{% block wiki_body %}
+
+{% endblock %}
+
+
+
diff --git a/simplewiki/templates/simplewiki_create.html b/simplewiki/templates/simplewiki_create.html
new file mode 100644
index 0000000000..b9b6eabedb
--- /dev/null
+++ b/simplewiki/templates/simplewiki_create.html
@@ -0,0 +1,16 @@
+{% extends "simplewiki_base.html" %}
+{% load i18n simplewiki_utils %}
+{% block wiki_page_title %}
+Create article
+{% endblock %}
+{% block wiki_body %}
+
+{% endblock %}
diff --git a/simplewiki/templates/simplewiki_edit.html b/simplewiki/templates/simplewiki_edit.html
new file mode 100644
index 0000000000..b0a7766d5d
--- /dev/null
+++ b/simplewiki/templates/simplewiki_edit.html
@@ -0,0 +1,17 @@
+{% extends "simplewiki_base.html" %}
+{% load i18n simplewiki_utils %}
+{% block wiki_page_title %}
+ {{wiki_article.title}}
+{% endblock %}
+
+{% block wiki_body %}
+
+{% endblock %}
diff --git a/simplewiki/templates/simplewiki_error.html b/simplewiki/templates/simplewiki_error.html
new file mode 100644
index 0000000000..7b7fb9bbe7
--- /dev/null
+++ b/simplewiki/templates/simplewiki_error.html
@@ -0,0 +1,98 @@
+{% extends "simplewiki_base.html" %}
+{% load i18n simplewiki_utils %}
+{% block wiki_page_title %}
+Oops...
+{% endblock %}
+
+{% block wiki_body %}
+
+
+
+
+
+
+
+
+
+
+ {% trans "Search" %}
+
+
+
+
+
+ {% if wiki_article %}
+
+
+
+
+
+
+
+
+
+
+
+ {% if wiki_article %}
+
+
+
+ {% endif %}
+
+
+
{% trans "This article has been locked" %}
+ {% endif %} ++ {% trans "Last modified" %}: {{ wiki_article.modified_on|date }}, {{ wiki_article.modified_on|time }} +
+ {% endif %} +
+
+
+
+
+
+
+
+
+
+
+ {% trans "Related articles" %}
+ {% if wiki_article.related.all %}
+
+ {% for rel in wiki_article.related.all %}
+
+ {% if wiki_write %}
+
+
+
+ {% endif %}
+ {{rel.title}}
+
+ {% endfor %}
+
({% trans "none" %})
+ {% endif %} + {% if wiki_write %} + + {% endif %} + +
+
+ {% endif %}
+
+
+
+
+
+
+
+
+
+ {% trans "Attachments" %}
+ {% if wiki_article.attachments %}
+ -
+ {% for a in wiki_article.attachments %}
+
- {{a.filename|slice:":13"|slice:":-3" }}{% if a.filename|slice:"10:" %}...{{ a.filename|slice:"-3:" }}{% endif %} ({{a.get_size|filesizeformat}}) + {% endfor %} +
({% trans "none" %})
+ {% endif %} + + {% if wiki_attachments_write %} + + + {% endif %} + +
+{{ wiki_error|safe }}
+
+{% if wiki_err_notfound %}
+{% if wiki_url %}
+
+{% endblock %}
+
diff --git a/simplewiki/templates/simplewiki_history.html b/simplewiki/templates/simplewiki_history.html
new file mode 100644
index 0000000000..aacbd3b5f6
--- /dev/null
+++ b/simplewiki/templates/simplewiki_history.html
@@ -0,0 +1,57 @@
+{% extends "simplewiki_base.html" %}
+{% load i18n simplewiki_utils %}
+{% block wiki_page_title %}
+ {{ wiki_article.title }}
+{% endblock %}
+{% block wiki_body %}
+
+{% endblock %}
diff --git a/simplewiki/templates/simplewiki_searchresults.html b/simplewiki/templates/simplewiki_searchresults.html
new file mode 100644
index 0000000000..a60487c4ea
--- /dev/null
+++ b/simplewiki/templates/simplewiki_searchresults.html
@@ -0,0 +1,21 @@
+{% extends "simplewiki_base.html" %}
+{% load i18n simplewiki_utils %}
+{% block wiki_page_title %}
+ {% if wiki_search_query %}
+ {% trans "Search results for" %} '{{ wiki_search_query|escape }}'
+ {% else %}
+ {% trans "Displaying all articles" %}
+ {% endif %}
+{% endblock %}
+
+{% block wiki_body %}
+ {% for article in wiki_search_results %}
+ {% if article.get_url %}
+ {{ article.get_url }}+The page you requested could not be found. +Click here to create it. +
+{% else %} ++Or maybe rather: Congratulations! It seems that there's no root +article, which is probably because you just installed simple-wiki +and your installation is working. Now you can create the root article. +Click here to create it. +
+{% endif %} +{% else %} + +{% if wiki_err_noparent %} ++You cannot create this page, because its parent +does not exist. Click here +to create it. +
+{% else %} + +{% if wiki_err_keyword %} ++The page you're trying to create {{wiki_url}} starts with _, which is reserved for internal use. +
+{% else %} + +{% if wiki_err_locked %} ++The article you are trying to modify is locked. +
+{% else %} + +{% if wiki_err_noread %} ++You do not have access to read this article. +
+{% else %} + +{% if wiki_err_nowrite %} ++You do not have access to edit this article. +
+{% else %} + +{% if wiki_err_noanon %} ++Anonymous attachments are not allowed. Try logging in. +
+{% else %} + +{% if wiki_err_create %} ++You do not have access to create this article. +
+{% else %} + +{% if wiki_err_encode %} ++The url you requested could not be handled by the wiki. +Probably you used a bad character in the URL. +Only use digits, English letters, underscore and dash. For instance +/wiki/An_Article-1 +
+ + +{% else %} ++An error has occured. +
+ + +{% endif %} +{% endif %} +{% endif %} +{% endif %} +{% endif %} +{% endif %} +{% endif %} +{% endif %} +{% endif %} + ++ {% else %} + /
+ {% endif %} + {% empty %} + {% trans "No articles were found!" %} + {% endfor %} +{% endblock %} diff --git a/simplewiki/templates/simplewiki_updateprogressbar.html b/simplewiki/templates/simplewiki_updateprogressbar.html new file mode 100644 index 0000000000..65f455518d --- /dev/null +++ b/simplewiki/templates/simplewiki_updateprogressbar.html @@ -0,0 +1,32 @@ +{% load i18n simplewiki_utils %} + +{% if started %} + +{% else %} +{% if finished %} + +{% else %} +{% if overwrite_warning %} + +{% else %} +{% if too_big %} + +{% else %} + +{% endif %} +{% endif %} +{% endif %} +{% endif %} diff --git a/simplewiki/templates/simplewiki_view.html b/simplewiki/templates/simplewiki_view.html new file mode 100644 index 0000000000..1c480d44fa --- /dev/null +++ b/simplewiki/templates/simplewiki_view.html @@ -0,0 +1,10 @@ +{% extends "simplewiki_base.html" %} +{% load i18n simplewiki_utils %} +{% block wiki_page_title %} +{{ wiki_article.title }} +{% endblock %} +{% block wiki_body %} +
+ {{ wiki_article.current_revision.contents_parsed|safe }}
+
+{% endblock %}
diff --git a/simplewiki/templatetags/__init__.py b/simplewiki/templatetags/__init__.py
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/simplewiki/templatetags/simplewiki_utils.py b/simplewiki/templatetags/simplewiki_utils.py
new file mode 100644
index 0000000000..5b8eccf910
--- /dev/null
+++ b/simplewiki/templatetags/simplewiki_utils.py
@@ -0,0 +1,17 @@
+from django import template
+from django.template.defaultfilters import stringfilter
+from simplewiki.settings import *
+from django.conf import settings
+from django.utils.http import urlquote as django_urlquote
+
+register = template.Library()
+
+@register.filter()
+def prepend_media_url(value):
+ """Prepend user defined media root to url"""
+ return settings.MEDIA_URL + value
+
+@register.filter()
+def urlquote(value):
+ """Prepend user defined media root to url"""
+ return django_urlquote(value)
\ No newline at end of file
diff --git a/simplewiki/tests.py b/simplewiki/tests.py
new file mode 100644
index 0000000000..2247054b35
--- /dev/null
+++ b/simplewiki/tests.py
@@ -0,0 +1,23 @@
+"""
+This file demonstrates two different styles of tests (one doctest and one
+unittest). These will both pass when you run "manage.py test".
+
+Replace these with more appropriate tests for your application.
+"""
+
+from django.test import TestCase
+
+class SimpleTest(TestCase):
+ def test_basic_addition(self):
+ """
+ Tests that 1 + 1 always equals 2.
+ """
+ self.failUnlessEqual(1 + 1, 2)
+
+__test__ = {"doctest": """
+Another way to test that 1 + 1 is equal to 2.
+
+>>> 1 + 1 == 2
+True
+"""}
+
diff --git a/simplewiki/urls.py b/simplewiki/urls.py
new file mode 100644
index 0000000000..1d8d3c246c
--- /dev/null
+++ b/simplewiki/urls.py
@@ -0,0 +1,18 @@
+from django.conf.urls.defaults import *
+
+urlpatterns = patterns('',
+ url(r'^$', 'simplewiki.views.root_redirect', name='wiki_root'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_edit/$', 'simplewiki.views.edit', name='wiki_edit'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_create/$', 'simplewiki.views.create', name='wiki_create'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_history/([0-9]*)/$', 'simplewiki.views.history', name='wiki_history'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_random/$', 'simplewiki.views.random_article', name='wiki_random'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_search/articles/$', 'simplewiki.views.search_articles', name='wiki_search_articles'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_search/related/$', 'simplewiki.views.search_add_related', name='search_related'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_related/add/$', 'simplewiki.views.add_related', name='add_related'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_related/remove/(\d+)$', 'simplewiki.views.remove_related', name='wiki_remove_relation'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_add_attachment/$', 'simplewiki.views_attachments.add_attachment', name='add_attachment'),
+ url(r'^/?([a-zA-Z\d/_-]*)/_view_attachment/(.+)?$', 'simplewiki.views_attachments.view_attachment', name='wiki_view_attachment'),
+# url(r'^/?([a-zA-Z\d/_-]*)/_view_attachment/?$', 'simplewiki.views_attachments.list_attachments', name='wiki_list_attachments'),
+ url(r'^/?([a-zA-Z\d/_-]*)$', 'simplewiki.views.view', name='wiki_view'),
+ url(r'^(.*)$', 'simplewiki.views.encode_err', name='wiki_encode_err')
+)
diff --git a/simplewiki/usage.txt b/simplewiki/usage.txt
new file mode 100644
index 0000000000..4a74ffaf8e
--- /dev/null
+++ b/simplewiki/usage.txt
@@ -0,0 +1,800 @@
+# Markdown: Syntax
+
+[TOC]
+
+## Overview
+
+### Philosophy
+
+Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
+
+Readability, however, is emphasized above all else. A Markdown-formatted
+document should be publishable as-is, as plain text, without looking
+like it's been marked up with tags or formatting instructions. While
+Markdown's syntax has been influenced by several existing text-to-HTML
+filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
+[Grutatext] [5], and [EtText] [6] -- the single biggest source of
+inspiration for Markdown's syntax is the format of plain text email.
+
+ [1]: http://docutils.sourceforge.net/mirror/setext.html
+ [2]: http://www.aaronsw.com/2002/atx/
+ [3]: http://textism.com/tools/textile/
+ [4]: http://docutils.sourceforge.net/rst.html
+ [5]: http://www.triptico.com/software/grutatxt.html
+ [6]: http://ettext.taint.org/doc/
+
+To this end, Markdown's syntax is comprised entirely of punctuation
+characters, which punctuation characters have been carefully chosen so
+as to look like what they mean. E.g., asterisks around a word actually
+look like \*emphasis\*. Markdown lists look like, well, lists. Even
+blockquotes look like quoted passages of text, assuming you've ever
+used email.
+
+### Automatic Escaping for Special Characters
+
+In HTML, there are two characters that demand special treatment: `<`
+and `&`. Left angle brackets are used to start tags; ampersands are
+used to denote HTML entities. If you want to use them as literal
+characters, you must escape them as entities, e.g. `<`, and
+`&`.
+
+Ampersands in particular are bedeviling for web writers. If you want to
+write about 'AT&T', you need to write '`AT&T`'. You even need to
+escape ampersands within URLs. Thus, if you want to link to:
+
+ http://images.google.com/images?num=30&q=larry+bird
+
+you need to encode the URL as:
+
+ http://images.google.com/images?num=30&q=larry+bird
+
+in your anchor tag `href` attribute. Needless to say, this is easy to
+forget, and is probably the single most common source of HTML validation
+errors in otherwise well-marked-up web sites.
+
+Markdown allows you to use these characters naturally, taking care of
+all the necessary escaping for you. If you use an ampersand as part of
+an HTML entity, it remains unchanged; otherwise it will be translated
+into `&`.
+
+So, if you want to include a copyright symbol in your article, you can write:
+
+ ©
+
+and Markdown will leave it alone. But if you write:
+
+ AT&T
+
+Markdown will translate it to:
+
+ AT&T
+
+Similarly, because Markdown supports [inline HTML](#html), if you use
+angle brackets as delimiters for HTML tags, Markdown will treat them as
+such. But if you write:
+
+ 4 < 5
+
+Markdown will translate it to:
+
+ 4 < 5
+
+However, inside Markdown code spans and blocks, angle brackets and
+ampersands are *always* encoded automatically. This makes it easy to use
+Markdown to write about HTML code. (As opposed to raw HTML, which is a
+terrible format for writing about HTML syntax, because every single `<`
+and `&` in your example code needs to be escaped.)
+
+
+* * *
+
+
+## Block Elements
+
+### Paragraphs and Line Breaks
+
+A paragraph is simply one or more consecutive lines of text, separated
+by one or more blank lines. (A blank line is any line that looks like a
+blank line -- a line containing nothing but spaces or tabs is considered
+blank.) Normal paragraphs should not be indented with spaces or tabs.
+
+The implication of the "one or more consecutive lines of text" rule is
+that Markdown supports "hard-wrapped" text paragraphs. This differs
+significantly from most other text-to-HTML formatters (including Movable
+Type's "Convert Line Breaks" option) which translate every line break
+character in a paragraph into a `` tag. + +When you *do* want to insert a `
` break tag using Markdown, you +end a line with two or more spaces, then type return. + +Yes, this takes a tad more effort to create a `
`, but a simplistic +"every line break is a `
`" rule wouldn't work for Markdown. +Markdown's email-style [blockquoting][bq] and multi-paragraph [list items][l] +work best -- and look better -- when you format them with hard breaks. + + [bq]: #blockquote + [l]: #list + +### Headers + +Markdown supports two styles of headers, [Setext] [1] and [atx] [2]. + +Setext-style headers are "underlined" using equal signs (for first-level +headers) and dashes (for second-level headers). For example: + + This is an H1 + ============= + + This is an H2 + ------------- + + This is an H3 + _____________ + +Any number of underlining `=`'s or `-`'s will work. + +Atx-style headers use 1-6 hash characters at the start of the line, +corresponding to header levels 1-6. For example: + + # This is an H1 + + ## This is an H2 + + ###### This is an H6 + +Optionally, you may "close" atx-style headers. This is purely +cosmetic -- you can use this if you think it looks better. The +closing hashes don't even need to match the number of hashes +used to open the header. (The number of opening hashes +determines the header level.) : + + # This is an H1 # + + ## This is an H2 ## + + ### This is an H3 ###### + + +### Blockquotes + +Markdown uses email-style `>` characters for blockquoting. If you're +familiar with quoting passages of text in an email message, then you +know how to create a blockquote in Markdown. It looks best if you hard +wrap the text and put a `>` before every line: + + > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet, + > consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. + > Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus. + > + > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse + > id sem consectetuer libero luctus adipiscing. + +Markdown allows you to be lazy and only put the `>` before the first +line of a hard-wrapped paragraph: + + > This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet, + consectetuer adipiscing elit. Aliquam hendrerit mi posuere lectus. + Vestibulum enim wisi, viverra nec, fringilla in, laoreet vitae, risus. + + > Donec sit amet nisl. Aliquam semper ipsum sit amet velit. Suspendisse + id sem consectetuer libero luctus adipiscing. + +Blockquotes can be nested (i.e. a blockquote-in-a-blockquote) by +adding additional levels of `>`: + + > This is the first level of quoting. + > + > > This is nested blockquote. + > + > Back to the first level. + +Blockquotes can contain other Markdown elements, including headers, lists, +and code blocks: + + > ## This is a header. + > + > 1. This is the first list item. + > 2. This is the second list item. + > + > Here's some example code: + > + > return shell_exec("echo $input | $markdown_script"); + +Any decent text editor should make email-style quoting easy. For +example, with BBEdit, you can make a selection and choose Increase +Quote Level from the Text menu. + + +### Lists + +Markdown supports ordered (numbered) and unordered (bulleted) lists. + +Unordered lists use asterisks, pluses, and hyphens -- interchangably +-- as list markers: + + * Red + * Green + * Blue + +is equivalent to: + + + Red + + Green + + Blue + +and: + + - Red + - Green + - Blue + +Ordered lists use numbers followed by periods: + + 1. Bird + 2. McHale + 3. Parish + +It's important to note that the actual numbers you use to mark the +list have no effect on the HTML output Markdown produces. The HTML +Markdown produces from the above list is: + +
-
+
- Bird +
- McHale +
- Parish +
` tags in the HTML output. For example, this input: + + * Bird + * Magic + +will turn into: + +
-
+
- Bird +
- Magic +
-
+
Bird
+ Magic
+
+
+
+It's worth noting that it's possible to trigger an ordered list by
+accident, by writing something like this:
+
+ 1986. What a great season.
+
+In other words, a *number-period-space* sequence at the beginning of a
+line. To avoid this, you can backslash-escape the period:
+
+ 1986\. What a great season.
+
+
+
+### Code Blocks
+
+Pre-formatted code blocks are used for writing about programming or
+markup source code. Rather than forming normal paragraphs, the lines
+of a code block are interpreted literally. Markdown wraps a code block
+in both `` and `` tags.
+
+To produce a code block in Markdown, simply indent every line of the
+block by at least 4 spaces or 1 tab. For example, given this input:
+
+ This is a normal paragraph:
+
+ This is a code block.
+
+Markdown will generate:
+
+ This is a normal paragraph:
+
+ This is a code block.
+
+
+One level of indentation -- 4 spaces or 1 tab -- is removed from each
+line of the code block. For example, this:
+
+ Here is an example of AppleScript:
+
+ tell application "Foo"
+ beep
+ end tell
+
+will turn into:
+
+ Here is an example of AppleScript:
+
+ tell application "Foo"
+ beep
+ end tell
+
+
+A code block continues until it reaches a line that is not indented
+(or the end of the article).
+
+Within a code block, ampersands (`&`) and angle brackets (`<` and `>`)
+are automatically converted into HTML entities. This makes it very
+easy to include example HTML source code using Markdown -- just paste
+it and indent it, and Markdown will handle the hassle of encoding the
+ampersands and angle brackets. For example, this:
+
+
+
+will turn into:
+
+ <div class="footer">
+ © 2004 Foo Corporation
+ </div>
+
+
+Regular Markdown syntax is not processed within code blocks. E.g.,
+asterisks are just literal asterisks within a code block. This means
+it's also easy to use Markdown to write about Markdown's own syntax.
+
+
+
+### Horizontal Rules
+
+You can produce a horizontal rule tag (`
`) by placing three or
+more hyphens, asterisks, or underscores on a line by themselves. If you
+wish, you may use spaces between the hyphens or asterisks. Each of the
+following lines will produce a horizontal rule:
+
+ * * *
+
+ ***
+
+ *****
+
+ - - -
+
+ ---------------------------------------
+
+
+## Span Elements
+
+### Links
+
+Markdown supports two style of links: *inline* and *reference*.
+
+In both styles, the link text is delimited by [square brackets].
+
+To create an inline link, use a set of regular parentheses immediately
+after the link text's closing square bracket. Inside the parentheses,
+put the URL where you want the link to point, along with an *optional*
+title for the link, surrounded in quotes. For example:
+
+ This is [an example](http://example.com/ "Title") inline link.
+
+ [This link](http://example.net/) has no title attribute.
+
+Will produce:
+
+ This is
+ an example inline link.
+
+ This link has no
+ title attribute.
+
+If you're referring to a local resource on the same server, you can
+use relative paths:
+
+ See my [About](/about/) page for details.
+
+Reference-style links use a second set of square brackets, inside
+which you place a label of your choosing to identify the link:
+
+ This is [an example][id] reference-style link.
+
+You can optionally use a space to separate the sets of brackets:
+
+ This is [an example] [id] reference-style link.
+
+Then, anywhere in the document, you define your link label like this,
+on a line by itself:
+
+ [id]: http://example.com/ "Optional Title Here"
+
+That is:
+
+* Square brackets containing the link identifier (optionally
+ indented from the left margin using up to three spaces);
+* followed by a colon;
+* followed by one or more spaces (or tabs);
+* followed by the URL for the link;
+* optionally followed by a title attribute for the link, enclosed
+ in double or single quotes, or enclosed in parentheses.
+
+The following three link definitions are equivalent:
+
+ [foo]: http://example.com/ "Optional Title Here"
+ [foo]: http://example.com/ 'Optional Title Here'
+ [foo]: http://example.com/ (Optional Title Here)
+
+**Note:** There is a known bug in Markdown.pl 1.0.1 which prevents
+single quotes from being used to delimit link titles.
+
+The link URL may, optionally, be surrounded by angle brackets:
+
+ [id]: I get 10 times more traffic from Google than from
+ Yahoo
+ or MSN.
+
+For comparison, here is the same paragraph written using
+Markdown's inline link style:
+
+ I get 10 times more traffic from [Google](http://google.com/ "Google")
+ than from [Yahoo](http://search.yahoo.com/ "Yahoo Search") or
+ [MSN](http://search.msn.com/ "MSN Search").
+
+The point of reference-style links is not that they're easier to
+write. The point is that with reference-style links, your document
+source is vastly more readable. Compare the above examples: using
+reference-style links, the paragraph itself is only 81 characters
+long; with inline-style links, it's 176 characters; and as raw HTML,
+it's 234 characters. In the raw HTML, there's more markup than there
+is text.
+
+With Markdown's reference-style links, a source document much more
+closely resembles the final output, as rendered in a browser. By
+allowing you to move the markup-related metadata out of the paragraph,
+you can add links without interrupting the narrative flow of your
+prose.
+
+### Emphasis
+
+Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
+emphasis. Text wrapped with one `*` or `_` will be wrapped with an
+HTML `` tag; double `*`'s or `_`'s will be wrapped with an HTML
+`` tag. E.g., this input:
+
+ *single asterisks*
+
+ _single underscores_
+
+ **double asterisks**
+
+ __double underscores__
+
+will produce:
+
+ single asterisks
+
+ single underscores
+
+ double asterisks
+
+ double underscores
+
+You can use whichever style you prefer; the lone restriction is that
+the same character must be used to open and close an emphasis span.
+
+Emphasis can be used in the middle of a word:
+
+ un*frigging*believable
+
+But if you surround an `*` or `_` with spaces, it'll be treated as a
+literal asterisk or underscore.
+
+To produce a literal asterisk or underscore at a position where it
+would otherwise be used as an emphasis delimiter, you can backslash
+escape it:
+
+ \*this text is surrounded by literal asterisks\*
+
+
+### Code
+
+To indicate a span of code, wrap it with backtick quotes (`` ` ``).
+Unlike a pre-formatted code block, a code span indicates code within a
+normal paragraph. For example:
+
+ Use the `printf()` function.
+
+will produce:
+
+ Use the printf() function.
+
+To include a literal backtick character within a code span, you can use
+multiple backticks as the opening and closing delimiters:
+
+ ``There is a literal backtick (`) here.``
+
+which will produce this:
+
+ There is a literal backtick (`) here.
+
+The backtick delimiters surrounding a code span may include spaces --
+one after the opening, one before the closing. This allows you to place
+literal backtick characters at the beginning or end of a code span:
+
+ A single backtick in a code span: `` ` ``
+
+ A backtick-delimited string in a code span: `` `foo` ``
+
+will produce:
+
+ A single backtick in a code span: `
+
+ A backtick-delimited string in a code span: `foo`
+
+With a code span, ampersands and angle brackets are encoded as HTML
+entities automatically, which makes it easy to include example HTML
+tags. Markdown will turn this:
+
+ Please don't use any `