From 57539d69e8ee1e86bd14c9e51273e576b2e38438 Mon Sep 17 00:00:00 2001 From: Artem Yunusov Date: Tue, 15 Jul 2008 18:18:09 +0500 Subject: Output bug fixed(stripping text data at the end of processing in _processPlaceholders). Ticket #5 fixed. --- tests/markdown-test/amps-and-angle-encoding.html | 4 +- .../markdown-documentation-basics.html | 67 ++-- tests/markdown-test/markdown-syntax.html | 373 +++++++++++---------- tests/markdown-test/strong-and-em-together.html | 4 +- tests/misc/arabic.html | 15 +- tests/misc/bidi.html | 12 +- tests/misc/blockquote.html | 19 +- tests/misc/funky-list.html | 13 +- tests/misc/japanese.html | 2 +- tests/misc/multi-test.html | 13 +- tests/misc/numeric-entity.html | 2 +- tests/misc/php.html | 2 +- tests/misc/russian.html | 3 +- tests/misc/underscores.html | 9 +- 14 files changed, 275 insertions(+), 263 deletions(-) (limited to 'tests') diff --git a/tests/markdown-test/amps-and-angle-encoding.html b/tests/markdown-test/amps-and-angle-encoding.html index 9c565e5..fc1b2c3 100644 --- a/tests/markdown-test/amps-and-angle-encoding.html +++ b/tests/markdown-test/amps-and-angle-encoding.html @@ -3,7 +3,7 @@

This & that.

4 < 5.

6 > 5.

-

Here's a linkwith an ampersand in the URL.

+

Here's a link with an ampersand in the URL.

Here's a link with an amersand in the link text: AT&T.

Here's an inline link.

-

Here's an inline link.

\ No newline at end of file +

Here's an inline link.

diff --git a/tests/markdown-test/markdown-documentation-basics.html b/tests/markdown-test/markdown-documentation-basics.html index 9c5259f..6755f77 100644 --- a/tests/markdown-test/markdown-documentation-basics.html +++ b/tests/markdown-test/markdown-documentation-basics.html @@ -8,16 +8,16 @@

Getting the Gist of Markdown's Formatting Syntax

This page offers a brief overview of what it's like to use Markdown. -The syntax pageprovides complete, detailed documentation for +The syntax page provides complete, detailed documentation for every feature, but Markdown should be very easy to pick up simply by looking at a few examples of it in action. The examples on this page are written in a before/after style, showing example syntax and the HTML output produced by Markdown.

-

It's also helpful to simply try Markdown out; the Dingusis a +

It's also helpful to simply try Markdown out; the Dingus is a web application that allows you type your own Markdown-formatted text and translate it to XHTML.

-Note: This document is itself written using Markdown; you + Note: This document is itself written using Markdown; you can see the source for it by adding '.text' to the URL.

Paragraphs, Headers, Blockquotes

A paragraph is simply one or more consecutive lines of text, separated @@ -33,7 +33,7 @@ HTML header level.

Blockquotes are indicated using email-style '>' angle brackets.

Markdown:

-A First Level Header
+  A First Level Header
 ====================
 
 A Second Level Header
@@ -57,7 +57,7 @@ dog's back.

Output:

-<h1>A First Level Header</h1>
+  <h1>A First Level Header</h1>
 
 <h2>A Second Level Header</h2>
 
@@ -83,7 +83,7 @@ dog's back.</p>
 
Markdown uses asterisks and underscores to indicate spans of emphasis.

 
Markdown:

 
-Some of these words *are emphasized*.
+  Some of these words *are emphasized*.
 Some of these words _are emphasized also_.
 
 Use two asterisks for **strong emphasis**.
@@ -92,7 +92,7 @@ Or, if you prefer, __use two underscores instead__.
 

 
Output:

 
-<p>Some of these words <em>are emphasized</em>.
+  <p>Some of these words <em>are emphasized</em>.
 Some of these words <em>are emphasized also</em>.</p>
 
 <p>Use two asterisks for <strong>strong emphasis</strong>.
@@ -104,28 +104,28 @@ Or, if you prefer, <strong>use two underscores instead</strong>.<
 +, and -) as list markers. These three markers are
 interchangable; this:

 
-*   Candy.
+  *   Candy.
 *   Gum.
 *   Booze.
 
 

 
this:

 
-+   Candy.
+  +   Candy.
 +   Gum.
 +   Booze.
 
 

 
and this:

 
--   Candy.
+  -   Candy.
 -   Gum.
 -   Booze.
 
 

 
all produce the same output:

 
-<ul>
+  <ul>
 <li>Candy.</li>
 <li>Gum.</li>
 <li>Booze.</li>
@@ -135,25 +135,25 @@ interchangable; this:

 
Ordered (numbered) lists use regular numbers, followed by periods, as
 list markers:

 
-1.  Red
+  1.  Red
 2.  Green
 3.  Blue
 
 

 
Output:

 
-<ol>
+  <ol>
 <li>Red</li>
 <li>Green</li>
 <li>Blue</li>
 </ol>
 
 

-
If you put blank lines between items, you'll get <p>tags for the
+
If you put blank lines between items, you'll get <p> tags for the
 list item text. You can create multi-paragraph list items by indenting
 the paragraphs by 4 spaces or 1 tab:

 
-*   A list item.
+  *   A list item.
 
     With multiple paragraphs.
 
@@ -162,7 +162,7 @@ the paragraphs by 4 spaces or 1 tab:

 

 
Output:

 
-<ul>
+  <ul>
 <li><p>A list item.</p>
 <p>With multiple paragraphs.</p></li>
 <li><p>Another item in the list.</p></li>
@@ -176,30 +176,30 @@ text you want to turn into a link.

 
Inline-style links use parentheses immediately after the link text.
 For example:

 
-This is an [example link](http://example.com/).
+  This is an [example link](http://example.com/).
 
 

 
Output:

 
-<p>This is an <a href="http://example.com/">
+  <p>This is an <a href="http://example.com/">
 example link</a>.</p>
 
 

 
Optionally, you may include a title attribute in the parentheses:

 
-This is an [example link](http://example.com/ "With a Title").
+  This is an [example link](http://example.com/ "With a Title").
 
 

 
Output:

 
-<p>This is an <a href="http://example.com/" title="With a Title">
+  <p>This is an <a href="http://example.com/" title="With a Title">
 example link</a>.</p>
 
 

 
Reference-style links allow you to refer to your links by names, which
 you define elsewhere in your document:

 
-I get 10 times more traffic from [Google][1] than from
+  I get 10 times more traffic from [Google][1] than from
 [Yahoo][2] or [MSN][3].
 
 [1]: http://google.com/        "Google"
@@ -209,16 +209,16 @@ you define elsewhere in your document:

 

 
Output:

 
-<p>I get 10 times more traffic from <a href="http://google.com/"
+  <p>I get 10 times more traffic from <a href="http://google.com/"
 title="Google">Google</a> than from <a href="http://search.yahoo.com/"
 title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/"
 title="MSN Search">MSN</a>.</p>
 
 

 
The title attribute is optional. Link names may contain letters,
-numbers and spaces, but are notcase sensitive:

+numbers and spaces, but are not case sensitive:

 
-I start my morning with a cup of coffee and
+  I start my morning with a cup of coffee and
 [The New York Times][NY Times].
 
 [ny times]: http://www.nytimes.com/
@@ -226,7 +226,7 @@ numbers and spaces, but are notcase sensitive:

 

 
Output:

 
-<p>I start my morning with a cup of coffee and
+  <p>I start my morning with a cup of coffee and
 <a href="http://www.nytimes.com/">The New York Times</a>.</p>
 
 

@@ -234,19 +234,19 @@ numbers and spaces, but are notcase sensitive:

 
Image syntax is very much like link syntax.

 
Inline (titles are optional):

 
-![alt text](/path/to/img.jpg "Title")
+  ![alt text](/path/to/img.jpg "Title")
 
 

 
Reference-style:

 
-![alt text][id]
+  ![alt text][id]
 
 [id]: /path/to/img.jpg "Title"
 
 

 
Both of the above examples produce the same output:

 
-<img src="/path/to/img.jpg" alt="alt text" title="Title" />
+  <img src="/path/to/img.jpg" alt="alt text" title="Title" />
 
 

 
Code

@@ -255,7 +255,7 @@ backtick quotes. Any ampersands (&) and angle brackets (&
 >) will automatically be translated into HTML entities. This makes
 it easy to use Markdown to write about HTML example code:

 
-I strongly recommend against using any `<blink>` tags.
+  I strongly recommend against using any `<blink>` tags.
 
 I wish SmartyPants used named entities like `&mdash;`
 instead of decimal-encoded entites like `&#8212;`.
@@ -263,7 +263,7 @@ instead of decimal-encoded entites like `&#8212;`.
 

 
Output:

 
-<p>I strongly recommend against using any
+  <p>I strongly recommend against using any
 <code>&lt;blink&gt;</code> tags.</p>
 
 <p>I wish SmartyPants used named entities like
@@ -273,10 +273,10 @@ entites like <code>&amp;#8212;</code>.</p>
 

 
To specify an entire block of pre-formatted code, indent every line of
 the block by 4 spaces or 1 tab. Just like with code spans, &, <,
-and >characters will be escaped automatically.

+and > characters will be escaped automatically.

 
Markdown:

 
-If you want your page to validate under XHTML 1.0 Strict,
+  If you want your page to validate under XHTML 1.0 Strict,
 you've got to put paragraph tags in your blockquotes:
 
     <blockquote>
@@ -286,7 +286,7 @@ you've got to put paragraph tags in your blockquotes:
 

 
Output:

 
-<p>If you want your page to validate under XHTML 1.0 Strict,
+  <p>If you want your page to validate under XHTML 1.0 Strict,
 you've got to put paragraph tags in your blockquotes:</p>
 
 <pre><code>&lt;blockquote&gt;
@@ -295,3 +295,4 @@ you've got to put paragraph tags in your blockquotes:</p>
 </code></pre>
 
 

+
diff --git a/tests/markdown-test/markdown-syntax.html b/tests/markdown-test/markdown-syntax.html
index 84fe3bd..b3df92f 100644
--- a/tests/markdown-test/markdown-syntax.html
+++ b/tests/markdown-test/markdown-syntax.html
@@ -7,74 +7,74 @@
     
  • Dingus
    • 
 
    
 
 
    
-Note: This document is itself written using Markdown; you
+  Note: This document is itself written using Markdown; you
 can see the source for it by adding '.text' to the URL.
    
 
    
 
    Overview
    
@@ -85,7 +85,7 @@ 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, atx, Textile, reStructuredText,
-Grutatext, and EtText-- the single biggest source of
+Grutatext, and EtText -- the single biggest source of
 inspiration for Markdown's syntax is the format of plain text email.
    
 
    To this end, Markdown's syntax is comprised entirely of punctuation
 characters, which punctuation characters have been carefully chosen so
@@ -95,13 +95,14 @@ blockquotes look like quoted passages of text, assuming you've ever
 used email.
    
 
    Inline HTML
    
 
    Markdown's syntax is intended for one purpose: to be used as a
-format for writingfor the web.
    
+format for writing for the web.
    
 
    Markdown is not a replacement for HTML, or even close to it. Its
 syntax is very small, corresponding only to a very small subset of
 HTML tags. The idea is not to create a syntax that makes it easier
 to insert HTML tags. In my opinion, HTML tags are already easy to
 insert. The idea for Markdown is to make it easy to read, write, and
-edit prose. HTML is a publishing format; Markdown is a writingformat. Thus, Markdown's formatting syntax only addresses issues that
+edit prose. HTML is a publishing format; Markdown is a writing
+format. Thus, Markdown's formatting syntax only addresses issues that
 can be conveyed in plain text.
    
 
    For any markup that is not covered by Markdown's syntax, you simply
 use HTML itself. There's no need to preface it or delimit it to
@@ -111,10 +112,10 @@ the tags.
    
 <table>, <pre>, <p>, 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. Markdown is smart enough not
-to add extra (unwanted) <p>tags around HTML block-level tags.
    
+to add extra (unwanted) <p> tags around HTML block-level tags.
    
 
    For example, to add an HTML table to a Markdown article:
    
 
    -This is a regular paragraph.
+  This is a regular paragraph.
 
 <table>
     <tr>
@@ -126,14 +127,14 @@ This is another regular paragraph.
 
 
    
 
    Note that Markdown formatting syntax is not processed within block-level
-HTML tags. E.g., you can't use Markdown-style *emphasis*inside an
+HTML tags. E.g., you can't use Markdown-style *emphasis* inside an
 HTML block.
    
 
    Span-level HTML tags -- e.g. <span>, <cite>, or <del> -- can be
 used anywhere in a Markdown paragraph, list item, or header. If you
 want, you can even use HTML tags instead of Markdown formatting; e.g. if
-you'd prefer to use HTML <a> or <img>tags instead of Markdown's
+you'd prefer to use HTML <a> or <img> tags instead of Markdown's
 link or image syntax, go right ahead.
    
-
    Unlike block-level HTML tags, Markdown syntax isprocessed within
+
    Unlike block-level HTML tags, Markdown syntax is processed within
 span-level tags.
    
 
    Automatic Escaping for Special Characters
    
 
    In HTML, there are two characters that demand special treatment: <
@@ -145,15 +146,15 @@ characters, you must escape them as entities, e.g. &lt;, and
 write about 'AT&T', you need to write 'AT&amp;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
+  http://images.google.com/images?num=30&q=larry+bird
 
 
    
 
    you need to encode the URL as:
    
 
    -http://images.google.com/images?num=30&amp;q=larry+bird
+  http://images.google.com/images?num=30&amp;q=larry+bird
 
 
    
-
    in your anchor tag hrefattribute. Needless to say, this is easy to
+
    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
@@ -162,36 +163,36 @@ an HTML entity, it remains unchanged; otherwise it will be translated
 into &amp;.
    
 
    So, if you want to include a copyright symbol in your article, you can write:
    
 
    -&copy;
+  &copy;
 
 
    
 
    and Markdown will leave it alone. But if you write:
    
 
    -AT&T
+  AT&T
 
 
    
 
    Markdown will translate it to:
    
 
    -AT&amp;T
+  AT&amp;T
 
 
    
 
    Similarly, because Markdown supports inline HTML, if you use
 angle brackets as delimiters for HTML tags, Markdown will treat them as
 such. But if you write:
    
 
    -4 < 5
+  4 < 5
 
 
    
 
    Markdown will translate it to:
    
 
    -4 &lt; 5
+  4 &lt; 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.)
    
+and & in your example code needs to be escaped.)
    
 
    
 
    Block Elements
    
 
    Paragraphs and Line Breaks
    
@@ -203,18 +204,19 @@ blank.) Normal paragraphs should not be intended with spaces or tabs.
    
 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 <br />tag.
    
-
    When you do want to insert a <br />break tag using Markdown, you
+character in a paragraph into a <br /> tag.
    
+
    When you do want to insert a <br /> 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 <br />, but a simplistic
 "every line break is a <br />" rule wouldn't work for Markdown.
-Markdown's email-style blockquoting and multi-paragraph list itemswork best -- and look better -- when you format them with hard breaks.
    
+Markdown's email-style blockquoting and multi-paragraph list items
+work best -- and look better -- when you format them with hard breaks.
    
 
    
-
    Markdown supports two styles of headers, Setextand atx.
    
+
    Markdown supports two styles of headers, Setext and atx.
    
 
    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 H1
 =============
 
 This is an H2
@@ -225,7 +227,7 @@ This is an H2
 
    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 H1
 
 ## This is an H2
 
@@ -238,7 +240,7 @@ 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 H1 #
 
 ## This is an H2 ##
 
@@ -249,9 +251,9 @@ determines the header level.) :
    
 
    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:
    
+wrap the text and put a > before every line:
    
 
    -> This is a blockquote with two paragraphs. Lorem ipsum dolor sit amet,
+  > 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.
 > 
@@ -259,10 +261,10 @@ wrap the text and put a >before every line:
    
 > id sem consectetuer libero luctus adipiscing.
     
 
    
-
    Markdown allows you to be lazy and only put the >before the first
+
    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,
+  > 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.
 
@@ -273,7 +275,7 @@ 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 the first level of quoting.
 >
 > > This is nested blockquote.
 >
@@ -283,7 +285,7 @@ adding additional levels of >:
    
 
    Blockquotes can contain other Markdown elements, including headers, lists,
 and code blocks:
    
 
    -> ## This is a header.
+  > ## This is a header.
 > 
 > 1.   This is the first list item.
 > 2.   This is the second list item.
@@ -301,28 +303,28 @@ Quote Level from the Text menu.
    
 
    Unordered lists use asterisks, pluses, and hyphens -- interchangably
 -- as list markers:
    
 
    -*   Red
+  *   Red
 *   Green
 *   Blue
 
 
    
 
    is equivalent to:
    
 
    -+   Red
+  +   Red
 +   Green
 +   Blue
 
 
    
 
    and:
    
 
    --   Red
+  -   Red
 -   Green
 -   Blue
 
 
    
 
    Ordered lists use numbers followed by periods:
    
 
    -1.  Bird
+  1.  Bird
 2.  McHale
 3.  Parish
 
@@ -331,7 +333,7 @@ Quote Level from the Text menu.
    
 list have no effect on the HTML output Markdown produces. The HTML
 Markdown produces from the above list is:
    
 
    -<ol>
+  <ol>
 <li>Bird</li>
 <li>McHale</li>
 <li>Parish</li>
@@ -340,14 +342,14 @@ Markdown produces from the above list is:
    
 
    
 
    If you instead wrote the list in Markdown like this:
    
 
    -1.  Bird
+  1.  Bird
 1.  McHale
 1.  Parish
 
 
    
 
    or even:
    
 
    -3. Bird
+  3. Bird
 1. McHale
 8. Parish
 
@@ -364,7 +366,7 @@ up to three spaces. List markers must be followed by one or more spaces
 or a tab.
    
 
    To make lists look nice, you can wrap items with hanging indents:
    
 
    -*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+  *   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.
@@ -373,7 +375,7 @@ or a tab.
    
 
    
 
    But if you want to be lazy, you don't have to:
    
 
    -*   Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
+  *   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.
@@ -381,15 +383,15 @@ Suspendisse id sem consectetuer libero luctus adipiscing.
 
 
    
 
    If list items are separated by blank lines, Markdown will wrap the
-items in <p>tags in the HTML output. For example, this input:
    
+items in <p> tags in the HTML output. For example, this input:
    
 
    -*   Bird
+  *   Bird
 *   Magic
 
 
    
 
    will turn into:
    
 
    -<ul>
+  <ul>
 <li>Bird</li>
 <li>Magic</li>
 </ul>
@@ -397,14 +399,14 @@ items in <p>tags in the HTML output. For example, this input:
 
    
 
    But this:
    
 
    -*   Bird
+  *   Bird
 
 *   Magic
 
 
    
 
    will turn into:
    
 
    -<ul>
+  <ul>
 <li><p>Bird</p></li>
 <li><p>Magic</p></li>
 </ul>
@@ -414,7 +416,7 @@ items in <p>tags in the HTML output. For example, this input:
 paragraph in a list item must be intended by either 4 spaces
 or one tab:
    
 
    -1.  This is a list item with two paragraphs. Lorem ipsum dolor
+  1.  This is a list item with two paragraphs. Lorem ipsum dolor
     sit amet, consectetuer adipiscing elit. Aliquam hendrerit
     mi posuere lectus.
 
@@ -429,7 +431,7 @@ or one tab:
    
 paragraphs, but here again, Markdown will allow you to be
 lazy:
    
 
    -*   This is a list item with two paragraphs.
+  *   This is a list item with two paragraphs.
 
     This is the second paragraph in the list item. You're
 only required to indent the first line. Lorem ipsum dolor
@@ -438,19 +440,19 @@ sit amet, consectetuer adipiscing elit.
 *   Another item in the same list.
 
 
    
-
    To put a blockquote within a list item, the blockquote's 
->delimiters need to be indented:
    
+
    To put a blockquote within a list item, the blockquote's >
+delimiters need to be indented:
    
 
    -*   A list item with a blockquote:
+  *   A list item with a blockquote:
 
     > This is a blockquote
     > inside a list item.
 
 
    
 
    To put a code block within a list item, the code block needs
-to be indented twice-- 8 spaces or two tabs:
    
+to be indented twice -- 8 spaces or two tabs:
    
 
    -*   A list item with a code block:
+  *   A list item with a code block:
 
         <code goes here>
 
@@ -458,31 +460,31 @@ to be indented twice-- 8 spaces or two tabs:
    
 
    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.
+  1986. What a great season.
 
 
    
-
    In other words, a number-period-spacesequence at the beginning of a
+
    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.
+  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 <pre> and <code>tags.
    
+in both <pre> and <code> 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 normal paragraph:
 
     This is a code block.
 
 
    
 
    Markdown will generate:
    
 
    -<p>This is a normal paragraph:</p>
+  <p>This is a normal paragraph:</p>
 
 <pre><code>This is a code block.
 </code></pre>
@@ -491,7 +493,7 @@ block by at least 4 spaces or 1 tab. For example, given this input:
    
 
    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:
+  Here is an example of AppleScript:
 
     tell application "Foo"
         beep
@@ -500,7 +502,7 @@ line of the code block. For example, this:
    
 
    
 
    will turn into:
    
 
    -<p>Here is an example of AppleScript:</p>
+  <p>Here is an example of AppleScript:</p>
 
 <pre><code>tell application "Foo"
     beep
@@ -516,14 +518,14 @@ 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:
    
 
    -    <div class="footer">
+      <div class="footer">
         &copy; 2004 Foo Corporation
     </div>
 
 
    
 
    will turn into:
    
 
    -<pre><code>&lt;div class="footer"&gt;
+  <pre><code>&lt;div class="footer"&gt;
     &amp;copy; 2004 Foo Corporation
 &lt;/div&gt;
 </code></pre>
@@ -538,7 +540,7 @@ 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:
    
 
    -* * *
+  * * *
 
 ***
 
@@ -558,16 +560,17 @@ _ _ _
 
    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 optionaltitle for the link, surrounded in quotes. For example:
    
+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 is [an example](http://example.com/ "Title") inline link.
 
 [This link](http://example.net/) has no title attribute.
 
 
    
 
    Will produce:
    
 
    -<p>This is <a href="http://example.com/" title="Title">
+  <p>This is <a href="http://example.com/" title="Title">
 an example</a> inline link.</p>
 
 <p><a href="http://example.net/">This link</a> has no
@@ -577,79 +580,79 @@ title attribute.</p>
 
    If you're referring to a local resource on the same server, you can
 use relative paths:
    
 
    -See my [About](/about/) page for details.
+  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.
+  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.
+  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"
+  [id]: http://example.com/  "Optional Title Here"
 
 
    
 
    That is:
    
 
      
-
    • Square brackets containing the link identifier (optionally
+  
    • 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
+  
    • 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.
      • 
 
    
 
    The link URL may, optionally, be surrounded by angle brackets:
    
 
    -[id]: <http://example.com/>  "Optional Title Here"
+  [id]: <http://example.com/>  "Optional Title Here"
 
 
    
 
    You can put the title attribute on the next line and use extra spaces
 or tabs for padding, which tends to look better with longer URLs:
    
 
    -[id]: http://example.com/longish/path/to/resource/here
+  [id]: http://example.com/longish/path/to/resource/here
     "Optional Title Here"
 
 
    
 
    Link definitions are only used for creating links during Markdown
 processing, and are stripped from your document in the HTML output.
    
-
    Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are notcase sensitive. E.g. these two links:
    
+
    Link definition names may constist of letters, numbers, spaces, and punctuation -- but they are not case sensitive. E.g. these two links:
    
 
    -[link text][a]
+  [link text][a]
 [link text][A]
 
 
    
 
    are equivalent.
    
-
    The implicit link nameshortcut allows you to omit the name of the
+
    The implicit link name shortcut allows you to omit the name of the
 link, in which case the link text itself is used as the name.
 Just use an empty set of square brackets -- e.g., to link the word
 "Google" to the google.com web site, you could simply write:
    
 
    -[Google][]
+  [Google][]
 
 
    
 
    And then define the link:
    
 
    -[Google]: http://google.com/
+  [Google]: http://google.com/
 
 
    
 
    Because link names may contain spaces, this shortcut even works for
 multiple words in the link text:
    
 
    -Visit [Daring Fireball][] for more information.
+  Visit [Daring Fireball][] for more information.
 
 
    
 
    And then define the link:
    
 
    -[Daring Fireball]: http://daringfireball.net/
+  [Daring Fireball]: http://daringfireball.net/
 
 
    
 
    Link definitions can be placed anywhere in your Markdown document. I
@@ -658,7 +661,7 @@ used, but if you want, you can put them all at the end of your
 document, sort of like footnotes.
    
 
    Here's an example of reference links in action:
    
 
    -I get 10 times more traffic from [Google] [1] than from
+  I get 10 times more traffic from [Google] [1] than from
 [Yahoo] [2] or [MSN] [3].
 
   [1]: http://google.com/        "Google"
@@ -668,7 +671,7 @@ document, sort of like footnotes.
    
 
    
 
    Using the implicit link name shortcut, you could instead write:
    
 
    -I get 10 times more traffic from [Google][] than from
+  I get 10 times more traffic from [Google][] than from
 [Yahoo][] or [MSN][].
 
   [google]: http://google.com/        "Google"
@@ -678,7 +681,7 @@ document, sort of like footnotes.
    
 
    
 
    Both of the above examples will produce the following HTML output:
    
 
    -<p>I get 10 times more traffic from <a href="http://google.com/"
+  <p>I get 10 times more traffic from <a href="http://google.com/"
 title="Google">Google</a> than from
 <a href="http://search.yahoo.com/" title="Yahoo Search">Yahoo</a>
 or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</p>
@@ -687,7 +690,7 @@ or <a href="http://search.msn.com/" title="MSN Search">MSN</a>.</
 
    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")
+  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").
 
@@ -708,9 +711,9 @@ prose.
    
 
    Markdown treats asterisks (*) and underscores (_) as indicators of
 emphasis. Text wrapped with one * or _ will be wrapped with an
 HTML <em> tag; double *'s or _'s will be wrapped with an HTML
-<strong>tag. E.g., this input:
    
+<strong> tag. E.g., this input:
    
 
    -*single asterisks*
+  *single asterisks*
 
 _single underscores_
 
@@ -721,7 +724,7 @@ __double underscores__
 
    
 
    will produce:
    
 
    -<em>single asterisks</em>
+  <em>single asterisks</em>
 
 <em>single underscores</em>
 
@@ -734,16 +737,16 @@ __double underscores__
 the same character must be used to open and close an emphasis span.
    
 
    Emphasis can be used in the middle of a word:
    
 
    -un*fucking*believable
+  un*fucking*believable
 
 
    
-
    But if you surround an * or _with spaces, it'll be treated as a
+
    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\*
+  \*this text is surrounded by literal asterisks\*
 
 
    
 
    Code
    
@@ -751,37 +754,37 @@ escape it:
    
 Unlike a pre-formatted code block, a code span indicates code within a
 normal paragraph. For example:
    
 
    -Use the `printf()` function.
+  Use the `printf()` function.
 
 
    
 
    will produce:
    
 
    -<p>Use the <code>printf()</code> function.</p>
+  <p>Use the <code>printf()</code> function.</p>
 
 
    
 
    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.``
+  ``There is a literal backtick (`) here.``
 
 
    
 
    which will produce this:
    
 
    -<p><code>There is a literal backtick (`) here.</code></p>
+  <p><code>There is a literal backtick (`) here.</code></p>
 
 
    
 
    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 single backtick in a code span: `` ` ``
 
 A backtick-delimited string in a code span: `` `foo` ``
 
 
    
 
    will produce:
    
 
    -<p>A single backtick in a code span: <code>`</code></p>
+  <p>A single backtick in a code span: <code>`</code></p>
 
 <p>A backtick-delimited string in a code span: <code>`foo`</code></p>
 
@@ -790,22 +793,22 @@ A backtick-delimited string in a code span: `` `foo` ``
 entities automatically, which makes it easy to include example HTML
 tags. Markdown will turn this:
    
 
    -Please don't use any `<blink>` tags.
+  Please don't use any `<blink>` tags.
 
 
    
 
    into:
    
 
    -<p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
+  <p>Please don't use any <code>&lt;blink&gt;</code> tags.</p>
 
 
    
 
    You can write this:
    
 
    -`&#8212;` is the decimal-encoded equivalent of `&mdash;`.
+  `&#8212;` is the decimal-encoded equivalent of `&mdash;`.
 
 
    
 
    to produce:
    
 
    -<p><code>&amp;#8212;</code> is the decimal-encoded
+  <p><code>&amp;#8212;</code> is the decimal-encoded
 equivalent of <code>&amp;mdash;</code>.</p>
 
 
    
@@ -816,44 +819,45 @@ placing images into a plain text document format.
    
 for links, allowing for two styles: inline and reference.
    
 
    Inline image syntax looks like this:
    
 
    -![Alt text](/path/to/img.jpg)
+  ![Alt text](/path/to/img.jpg)
 
 ![Alt text](/path/to/img.jpg "Optional title")
 
 
    
 
    That is:
    
 
      
-
    • An exclamation mark: !;
      • 
-
    • followed by a set of square brackets, containing the altattribute text for the image;
      • 
-
    • followed by a set of parentheses, containing the URL or path to
-the image, and an optional titleattribute enclosed in double
+  
    • An exclamation mark: !;
      • 
+  
    • followed by a set of square brackets, containing the alt
+attribute text for the image;
      • 
+  
    • followed by a set of parentheses, containing the URL or path to
+the image, and an optional title attribute enclosed in double
 or single quotes.
      • 
 
    
 
    Reference-style image syntax looks like this:
    
 
    -![Alt text][id]
+  ![Alt text][id]
 
 
    
 
    Where "id" is the name of a defined image reference. Image references
 are defined using syntax identical to link references:
    
 
    -[id]: url/to/image  "Optional title attribute"
+  [id]: url/to/image  "Optional title attribute"
 
 
    
 
    As of this writing, Markdown has no syntax for specifying the
 dimensions of an image; if this is important to you, you can simply
-use regular HTML <img>tags.
    
+use regular HTML <img> tags.
    
 
    
 
    Miscellaneous
    
 
    
 
    Markdown supports a shortcut style for creating "automatic" links for URLs and email addresses: simply surround the URL or email address with angle brackets. What this means is that if you want to show the actual text of a URL or email address, and also have it be a clickable link, you can do this:
    
 
    -<http://example.com/>
+  <http://example.com/>
 
 
    
 
    Markdown will turn this into:
    
 
    -<a href="http://example.com/">http://example.com/</a>
+  <a href="http://example.com/">http://example.com/</a>
 
 
    
 
    Automatic links for email addresses work similarly, except that
@@ -861,12 +865,12 @@ Markdown will also perform a bit of randomized decimal and hex
 entity-encoding to help obscure your address from address-harvesting
 spambots. For example, Markdown will turn this:
    
 
    -<address@example.com>
+  <address@example.com>
 
 
    
 
    into something like this:
    
 
    -<a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
+  <a href="&#x6D;&#x61;i&#x6C;&#x74;&#x6F;:&#x61;&#x64;&#x64;&#x72;&#x65;
 &#115;&#115;&#64;&#101;&#120;&#x61;&#109;&#x70;&#x6C;e&#x2E;&#99;&#111;
 &#109;">&#x61;&#x64;&#x64;&#x72;&#x65;&#115;&#115;&#64;&#101;&#120;&#x61;
 &#109;&#x70;&#x6C;e&#x2E;&#99;&#111;&#109;</a>
@@ -881,15 +885,15 @@ will probably eventually start receiving spam.)
    
 
    Markdown allows you to use backslash escapes to generate literal
 characters which would otherwise have special meaning in Markdown's
 formatting syntax. For example, if you wanted to surround a word with
-literal asterisks (instead of an HTML <em>tag), you can backslashes
+literal asterisks (instead of an HTML <em> tag), you can backslashes
 before the asterisks, like this:
    
 
    -\*literal asterisks\*
+  \*literal asterisks\*
 
 
    
 
    Markdown provides backslash escapes for the following characters:
    
 
    -\   backslash
+  \   backslash
 `   backtick
 *   asterisk
 _   underscore
@@ -903,3 +907,4 @@ _   underscore
 !   exclamation mark
 
 
    
+
diff --git a/tests/markdown-test/strong-and-em-together.html b/tests/markdown-test/strong-and-em-together.html
index 8a40b58..04c1850 100644
--- a/tests/markdown-test/strong-and-em-together.html
+++ b/tests/markdown-test/strong-and-em-together.html
@@ -5,7 +5,7 @@
 
    
 
    So is 
 this
-word.
    
+ word.
    
 
    
 
 This is strong and em.
@@ -13,4 +13,4 @@
 
    
 
    So is 
 this
-word.
    
\ No newline at end of file
+     word.
    
diff --git a/tests/misc/arabic.html b/tests/misc/arabic.html
index ab4cc13..830d62a 100644
--- a/tests/misc/arabic.html
+++ b/tests/misc/arabic.html
@@ -1,17 +1,17 @@
 
    بايثون
    
 
    
-بايثونلغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (OOP) وقابلة للتطوير بالإضافة إلى أنها مجانية و مفتوحة المصدر. صُنفت بالأساس كلغة تفسيرية ، بايثون مصممة أصلاً للأداء بعض المهام الخاصة أو المحدودة. إلا أنه يمكن استخدامها بايثون لإنجاز المشاريع الضخمه كأي لغة برمجية أخرى،  غالباً ما يُنصح المبتدئين في ميدان البرمجة بتعلم هذه اللغة لأنها من بين أسهل اللغات البرمجية تعلماً.
    
+  بايثون لغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (OOP) وقابلة للتطوير بالإضافة إلى أنها مجانية و مفتوحة المصدر. صُنفت بالأساس كلغة تفسيرية ، بايثون مصممة أصلاً للأداء بعض المهام الخاصة أو المحدودة. إلا أنه يمكن استخدامها بايثون لإنجاز المشاريع الضخمه كأي لغة برمجية أخرى،  غالباً ما يُنصح المبتدئين في ميدان البرمجة بتعلم هذه اللغة لأنها من بين أسهل اللغات البرمجية تعلماً.
    
 
    نشأت بايثون في مركز CWI (مركز العلوم والحاسب الآلي) بأمستردام على يد جويدو فان رُزوم. تم تطويرها بلغة C. أطلق فان رُزوم اسم "بايثون" على لغته تعبيرًا عن إعجابه بفِرقَة مسرحية هزلية شهيرة من بريطانيا، كانت تطلق على نفسها اسم مونتي بايثون Monty Python.
    
 
    تتميز بايثون بمجتمعها النشط ، كما أن لها الكثير من المكتبات البرمجية ذات الأغراض الخاصة والتي برمجها أشخاص من مجتمع هذه اللغة ، مثلاً مكتبة PyGame التي توفر مجموعه من الوظائف من اجل برمجة الالعاب. ويمكن لبايثون التعامل مع العديد من أنواع قواعد البيانات مثل MySQL وغيره.
    
 
    أمثلة
    
 
    مثال Hello World!
    
 
    -print "Hello World!"
+  print "Hello World!"
 
 
    
 
    مثال لاستخراج المضروب Factorial :
    
 
    -num = 1
+  num = 1
 x = raw_input('Insert the number please ')
 x = int(x)
 
@@ -27,8 +27,9 @@ else:
 
    
 
    وصلات خارجية
    
 
-
    بذرة حاس
    
+
     بذرة حاس 
    
+
diff --git a/tests/misc/bidi.html b/tests/misc/bidi.html
index 1959181..e7759f1 100644
--- a/tests/misc/bidi.html
+++ b/tests/misc/bidi.html
@@ -1,17 +1,17 @@
 
    
   Python（パイソン）は、Guido van Rossum によって作られたオープンソースのオブジェクト指向スクリプト言語。Perlとともに欧米で広く普及している。イギリスのテレビ局 BBC が製作したコメディ番組『空飛ぶモンティ・パイソン』にちなんで名付けられた。 (Pythonには、爬虫類のニシキヘビの意味があり、Python言語のマスコットやアイコンとして使われることがある。)
    
 
    |||||||||||||||||||||||||||||THIS SHOULD BE LTR|||||||||||||||||||||||||
    
-
    |||||||||||||||||||||||||||||THIS SHOULD BE RTL||||||||||||||||||||||||| 
    
-
    (بايثونلغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (THIS SHOULD BE LTR ) وقابلة للتطوير    بالإضافة إلى أنها مجانية و مفتوح
    
+
    |||||||||||||||||||||||||||||THIS SHOULD BE RTL|||||||||||||||||||||||||  
    
+
    (بايثون لغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (THIS SHOULD BE LTR ) وقابلة للتطوير    بالإضافة إلى أنها مجانية و مفتوح 
    
 
    پایتون زبان برنامه‌نویسی تفسیری و سطح بالا ، شی‌گرا و یک زبان برنامه‌نویسی تفسیری سمت سرور قدرتمند است که توسط گیدو ون روسوم در سال ۱۹۹۰ ساخته شد. این زبان در ویژگی‌ها شبیه پرل، روبی، اسکیم، اسمال‌تاک و تی‌سی‌ال است و از مدیریت خودکار حافظه استفاده می‌کند
    
 
    Python，是一种面向对象的、直譯式的计算机程序设计语言，也是一种功能强大而完善的通用型语言，已经具有十多年的发展历史，成熟且稳定。
    
 
    ބްލޫ ވޭލްގެ ދޫ މަތީގައި އެއްފަހަރާ 50 މީހުންނަށް ތިބެވިދާނެވެ. ބޮޑު މަހުގެ ދުލަކީ އެހާމެ ބޮޑު އެއްޗެކެވެ.
    
 
    
-  உருது13ஆம் நூற்றாண்டில் உருவான ஒரு இந்தோ-ஐரோப்பிய மொழியாகும். உருது, ஹிந்தியுடன் சேர்த்து "ஹிந்துஸ்தானி" என அழைக்கப்படுகின்றது. மண்டரின், ஆங்கிலம் ஆகியவற்றுக்கு அடுத்தபடியாக மூன்றாவது கூடிய அளவு மக்களால் புரிந்து கொள்ளப்படக்கூடியது ஹிந்துஸ்தானியேயாகும். தாய் மொழியாகப் பேசுபவர்கள் எண்ணிக்கையின் அடிப்படையில் உருது உலகின் 20 ஆவது பெரிய மொழியாகும். 6 கோடி மக்கள் இதனைத் தாய் மொழியாகக் கொண்டுள்ளார்கள். இரண்டாவது மொழியாகக் கொண்டுள்ளவர்கள் உட்பட 11 கோடிப் பேர் இதனைப் பேசுகிறார்கள். உருது பாகிஸ்தானின் அரசகரும மொழியாகவும், இந்தியாவின் அரசகரும மொழிகளுள் ஒன்றாகவும் விளங்குகிறது.
    
+  உருது 13ஆம் நூற்றாண்டில் உருவான ஒரு இந்தோ-ஐரோப்பிய மொழியாகும். உருது, ஹிந்தியுடன் சேர்த்து "ஹிந்துஸ்தானி" என அழைக்கப்படுகின்றது. மண்டரின், ஆங்கிலம் ஆகியவற்றுக்கு அடுத்தபடியாக மூன்றாவது கூடிய அளவு மக்களால் புரிந்து கொள்ளப்படக்கூடியது ஹிந்துஸ்தானியேயாகும். தாய் மொழியாகப் பேசுபவர்கள் எண்ணிக்கையின் அடிப்படையில் உருது உலகின் 20 ஆவது பெரிய மொழியாகும். 6 கோடி மக்கள் இதனைத் தாய் மொழியாகக் கொண்டுள்ளார்கள். இரண்டாவது மொழியாகக் கொண்டுள்ளவர்கள் உட்பட 11 கோடிப் பேர் இதனைப் பேசுகிறார்கள். உருது பாகிஸ்தானின் அரசகரும மொழியாகவும், இந்தியாவின் அரசகரும மொழிகளுள் ஒன்றாகவும் விளங்குகிறது.
    
 
    اردو ہندوآریائی زبانوں کی ہندويورپی شاخ کی ایک زبان ہے جو تيرھويں صدی ميں بر صغير ميں پيدا ہوئی ـ اردو پاکستان کی سرکاری زبان ہے اور بھارت کی سرکاری زبانوں ميں سے ايک ہے۔ اردو بھارت ميں 5 کروڑ اور پاکستان ميں 1 کروڑ لوگوں کی مادری زبان ہے مگر اسے بھارت اور پاکستان کے تقریباً 50 کروڑ لوگ بول اور سمجھ سکتے ھیں ۔ جن میں سے تقریباً 10.5 کروڑ لوگ اسے باقاعدہ بولتے ھیں۔
    
 
    بايثون
    
 
    
-  بايثونلغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (OOP) وقابلة للتطوير بالإضافة إلى أنها مجانية و مفتوحة المصدر. صُنفت بالأساس كلغة تفسيرية ، بايثون مصممة أصلاً للأداء بعض المهام الخاصة أو المحدودة. إلا أنه يمكن استخدامها بايثون لإنجاز المشاريع الضخمه كأي لغة برمجية أخرى،  غالباً ما يُنصح المبتدئين في ميدان البرمجة بتعلم هذه اللغة لأنها من بين أسهل اللغات البرمجية تعلماً.
    
+  بايثون لغة برمجة حديثة بسيطة، واضحة، سريعة ، تستخدم أسلوب البرمجة الكائنية (OOP) وقابلة للتطوير بالإضافة إلى أنها مجانية و مفتوحة المصدر. صُنفت بالأساس كلغة تفسيرية ، بايثون مصممة أصلاً للأداء بعض المهام الخاصة أو المحدودة. إلا أنه يمكن استخدامها بايثون لإنجاز المشاريع الضخمه كأي لغة برمجية أخرى،  غالباً ما يُنصح المبتدئين في ميدان البرمجة بتعلم هذه اللغة لأنها من بين أسهل اللغات البرمجية تعلماً.
    
 
    |||||||||||||||||||||||||||||THIS SHOULD BE RTL|||||||||||||||||||||||||
    
 
    (نشأت بايثون في مركز CWI (مركز العلوم والحاسب الآلي) بأمستردام على يد جويدو فان رُزوم. تم تطويرها بلغة C. أطلق فان رُزوم اسم "بايثون" على لغته تعبيرًا عن إعجابه بفِرقَة مسرحية هزلية شهيرة من بريطانيا، كانت تطلق على نفسها اسم مونتي بايثون Monty Python.
    
 
    تتميز بايثون بمجتمعها النشط ، كما أن لها الكثير من المكتبات البرمجية ذات الأغراض الخاصة والتي برمجها أشخاص من مجتمع هذه اللغة ، مثلاً مكتبة PyGame التي توفر مجموعه من الوظائف من اجل برمجة الالعاب. ويمكن لبايثون التعامل مع العديد من أنواع قواعد البيانات مثل MySQL وغيره.
    
@@ -43,9 +43,9 @@ else:
     الموقع الرسمي للغة بايثون
   
 
-
    بذرة حاس
    
+
     بذرة حاس 
    
 
    
-  Недвард «Нед» Фландерс(Nedward «Ned» Flanders) — вымышленный персонаж мультсериала «[Симпсоны][]», озвученный Гарри Ширером. Он и его семья живут по соседству от семьи Симпсонов. Набожный христианин, Нед является одним из столпов морали Спрингфилда. В эпизоде «Alone Again, Natura-Diddily»  он овдовел, его жена Мод погибла в результате несчастного случая.
    
+  Недвард «Нед» Фландерс (Nedward «Ned» Flanders) — вымышленный персонаж мультсериала «[Симпсоны][]», озвученный Гарри Ширером. Он и его семья живут по соседству от семьи Симпсонов. Набожный христианин, Нед является одним из столпов морали Спрингфилда. В эпизоде «Alone Again, Natura-Diddily»  он овдовел, его жена Мод погибла в результате несчастного случая. 
    
 
    Нед был одним из первых персонажей в мультсериале, который не был членом семьи Симпсонов. Начиная с первых серий, он регулярно появляется в «Симпсонах». Считается, что Нед Фландерс был назван в честь улицы Northeast Flanders St. в Портленде, Орегон, родном городе создателя мультсериала Мэтта Грейнинга]]. Надпись на указателе улицы NE Flanders St. хулиганы часто исправляли на NED Flanders St.
 
    
 
diff --git a/tests/misc/blockquote.html b/tests/misc/blockquote.html
index 08289b4..429c6d0 100644
--- a/tests/misc/blockquote.html
+++ b/tests/misc/blockquote.html
@@ -1,24 +1,25 @@
 
    
-
    blockquote with no whitespace before >.
    
+  
    blockquote with no whitespace before >.
    
 
    
 
    foo
    
 
    
-
    blockquote with one space before the >.
    
+  
    blockquote with one space before the >.
    
 
    
 
    bar
    
 
    
-
    blockquote with 2 spaces.
    
+  
    blockquote with 2 spaces.
    
 
    
 
    baz
    
-
    > this has three spaces so its a paragraph.
    
+
       > this has three spaces so its a paragraph.
    
 
    blah
    
 
    -> this one had four so it's a code block.
+  > this one had four so it's a code block.
 
 
    
 
    
-
    
-
    this nested blockquote has 0 on level one and 3 (one after the first >+ 2 more) on level 2.
    
+  
    
+    
    this nested blockquote has 0 on level one and 3 (one after the first > + 2 more) on level 2.
    
+  
    
+  
       > and this has 4 on level 2 - another code block.
    
 
    
-
    > and this has 4 on level 2 - another code block.
    
-
    
\ No newline at end of file
+
diff --git a/tests/misc/funky-list.html b/tests/misc/funky-list.html
index a1aa372..f489d56 100644
--- a/tests/misc/funky-list.html
+++ b/tests/misc/funky-list.html
@@ -1,11 +1,12 @@
 
      
-
    1. this starts a list withnumbers
      2. 
-
    2. this will show as number "2"
      3. 
-
    3. this will show as number "3."
      4. 
-
    4. any number, +, -, or * will keep the list going.
      5. 
+  
    5. this starts a list with numbers
      6. 
+  
    6. this will show as number "2"
      7. 
+  
    7. this will show as number "3."
      8. 
+  
    8. any number, +, -, or * will keep the list going.
      9. 
 
    
 
    aaaaaaaaaaaaaaa
    
 
      
-
    • now a normal list
      • 
-
    • and more
      • 
+  
    • now a normal list
      • 
+  
    • and more
      • 
 
    
+
diff --git a/tests/misc/japanese.html b/tests/misc/japanese.html
index 3fda1c1..ae1df5d 100644
--- a/tests/misc/japanese.html
+++ b/tests/misc/japanese.html
@@ -9,5 +9,5 @@
   
  • オブジェクトのメンバに対するアクセスが制限されていない。（属性や専用のメソッドフックを実装することによって制限は可能。）
    • 
   
  • モジュール、クラス、オブジェクト等の言語の要素が内部からアクセス可能であり、リフレクションを利用した記述が可能。
    • 
 
-
    また、Pythonではインデントによりブロックを指定する構文を採用している（⇒オフサイドルール）。この構文はPythonに慣れたユーザからは称賛をもって受け入れられているが、他の言語のユーザからは批判も多い。このほかにも、大きすぎる実行ファイルや、Javaに比べて遅い処理速度などが欠点として指摘されている。しかし プロトタイピングの際にはこれらの点はさして問題とはならないことから、研究開発部門では頻繁に利用されている。
    
+
    また、Pythonではインデントによりブロックを指定する構文を採用している（⇒オフサイドルール）。この構文はPythonに慣れたユーザからは称賛をもって受け入れられているが、他の言語のユーザからは批判も多い。このほかにも、大きすぎる実行ファイルや、Javaに比べて遅い処理速度などが欠点として指摘されている。しかし プロトタイピング の際にはこれらの点はさして問題とはならないことから、研究開発部門では頻繁に利用されている。
    
 
diff --git a/tests/misc/multi-test.html b/tests/misc/multi-test.html
index fbb37f3..1fc7bdb 100644
--- a/tests/misc/multi-test.html
+++ b/tests/misc/multi-test.html
@@ -3,21 +3,22 @@
 
    Blah blah blah http://www.slashdot.org
 
    
 
      
-
    • Basic list
      • 
-
    • Basic list 2
      • 
+  
    • Basic list
      • 
+  
    • Basic list 2
      • 
 
    
 
    addss
    
 
      
-
    • Lazy list
      • 
+  
    • Lazy list
      • 
 
    
-
    An example(oops)
    
+
    An example (oops)
    
 
    Now, let's use a footnote[^1].  Not bad, eh?
 Let's continue.
    
-
    [^1]: Here is the text of the footnote
+
      [^1]: Here is the text of the footnote
     continued on several lines.
     some more of the footnote, etc.
    
 
    -Actually, another paragraph too.
+  Actually, another paragraph too.
 
 
    
 
    And then there is a little bit of text.
    
+
diff --git a/tests/misc/numeric-entity.html b/tests/misc/numeric-entity.html
index 2fa51aa..720a601 100644
--- a/tests/misc/numeric-entity.html
+++ b/tests/misc/numeric-entity.html
@@ -1,4 +1,4 @@
 
    
 user@gmail.com
 
    
-
    This is an entity: ê
    
\ No newline at end of file
+
    This is an entity: ê 
    
diff --git a/tests/misc/php.html b/tests/misc/php.html
index db0333c..66bc8d1 100644
--- a/tests/misc/php.html
+++ b/tests/misc/php.html
@@ -6,4 +6,4 @@
 
    
 
    This shouldn't
    
 
    
-
    <?php echo "not_block_level";?>
    
\ No newline at end of file
+
     <?php echo "not_block_level";?>
    
diff --git a/tests/misc/russian.html b/tests/misc/russian.html
index fef2ebc..06efb99 100644
--- a/tests/misc/russian.html
+++ b/tests/misc/russian.html
@@ -1,8 +1,9 @@
 
    Недвард «Нед» Фландерс
    
 
    
-Недвард «Нед» Фландерс(Nedward «Ned» Flanders) — вымышленный персонаж мультсериала «[Симпсоны][]», озвученный Гарри Ширером. Он и его семья живут по соседству от семьи Симпсонов. Набожный христианин, Нед является одним из столпов морали Спрингфилда. В эпизоде «Alone Again, Natura-Diddily»  он овдовел, его жена Мод погибла в результате несчастного случая.
    
+  Недвард «Нед» Фландерс (Nedward «Ned» Flanders) — вымышленный персонаж мультсериала «[Симпсоны][]», озвученный Гарри Ширером. Он и его семья живут по соседству от семьи Симпсонов. Набожный христианин, Нед является одним из столпов морали Спрингфилда. В эпизоде «Alone Again, Natura-Diddily»  он овдовел, его жена Мод погибла в результате несчастного случая. 
    
 
    Нед был одним из первых персонажей в мультсериале, который не был членом семьи Симпсонов. Начиная с первых серий, он регулярно появляется в «Симпсонах». Считается, что Нед Фландерс был назван в честь улицы Northeast Flanders St. в Портленде, Орегон, родном городе создателя мультсериала Мэтта Грейнинга]]. Надпись на указателе улицы NE Flanders St. хулиганы часто исправляли на NED Flanders St.
 
    
 
    Биография
    
 
    Нед Фландерс родился в Нью-Йорке, его родители были битниками. Его отец в точности похож на взрослого Неда, только он носил козлиную бородку. Их отказ от воспитания Неда и то, что они, в общем-то, были плохими родителями («мы ничего в этом не понимаем и не знаем как начать») привело к тому, что Нед превратился в ужасного сорванца. В конце концов они согласились на экспериментальную восьмимесячную шлепологическую терапию Миннесотского Университета (воспоминания Неда в эпизоде «Hurricane Neddy»), которая научила его подавлять чувство злости. Побочным эфектом терапии стало то, что Нед стал ненавидеть своих родителей (это одна из двух вещей которые ненавидит Фландерс, вторая — отделения почты, чьи длинные очереди, суета и угрюмый персонал раздражают его).
    
 
    У Неда есть странная привычка добавлять «дидли», «дадли» и другие бессмысленные слова в свои фразы при разговоре, например: «Hi-diddly-ho, neighbor-ino» («Приветик, соседушка»). Это результат сублимации его злости, вызванной сдерживанием гнева, который не имеет никакого другого выхода.
    
+
diff --git a/tests/misc/underscores.html b/tests/misc/underscores.html
index 43b488f..fa9e642 100644
--- a/tests/misc/underscores.html
+++ b/tests/misc/underscores.html
@@ -1,8 +1,9 @@
 
    THIS_SHOULD_STAY_AS_IS
    
 
    Here is some emphasis, ok?
    
-
    Ok, at least thisshould work.
    
+
    Ok, at least this should work.
    
 
    THISSHOULDSTAY
    
-
    Here is some strongstuff.
    
+
    Here is some strong stuff.
    
 
    THIS
-SHOULD
-STAY?
    
\ No newline at end of file
+    SHOULD
+  STAY?
    
+
-- 
cgit v1.2.3