org-ruby 0.5.1 → 0.5.2

data/spec/html_examples/export-title.html

@@ -1,2 +1,2 @@
-<p class="title">Export Title</p>
-<p>This simple org document should get a title from the <code>TITLE</code> option at the front of the file.</p>
+<p class="title">Export Title</p>
+<p>This simple org document should get a title from the <code>TITLE</code> option at the front of the file.</p>

data/spec/html_examples/export-title.org

@@ -1,4 +1,4 @@
-#+TITLE:   Export Title
-
-This simple org document should get a title from the =TITLE= option at
-the front of the file.
+#+TITLE:   Export Title
+
+This simple org document should get a title from the =TITLE= option at
+the front of the file.

data/spec/html_examples/html-literal.html

@@ -1,2 +1,2 @@
-<p class="title">HTML literals</p>
-<p>ORG escapes HTML by default. This should &lt;b&gt;not be bold text!&lt;/b&gt; Instead, it should look like regular text with some HTML tags around it.</p>
+<p class="title">HTML literals</p>
+<p>ORG escapes HTML by default. This should &lt;b&gt;not be bold text!&lt;/b&gt; Instead, it should look like regular text with some HTML tags around it.</p>

data/spec/html_examples/html-literal.org

@@ -1,6 +1,6 @@
-HTML literals
-
-ORG escapes HTML by default. This should <b>not be bold text!</b>
-Instead, it should look like regular text with some HTML tags around
-it.
-
+HTML literals
+
+ORG escapes HTML by default. This should <b>not be bold text!</b>
+Instead, it should look like regular text with some HTML tags around
+it.
+

data/spec/html_examples/inline-formatting.html

@@ -1,10 +1,10 @@
-<p class="title">Inline Formatting</p>
-<p>I want to make sure I handle all inline formatting. I need to handle <b>bold</b>, <i>italic</i>, <code>code</code>, <code>verbatim</code>, <span style="text-decoration:underline;">underline</span>, <del>strikethrough</del>.</p>
-<p>In addition, I need to make sure I can handle links. We&#8217;ve got simple links, like this:</p>
-<ul>
-  <li><a href="http://www.bing.com">http://www.bing.com</a></li>
-  <li><a href="http://www.google.com">http://www.google.com</a></li>
-  <li>http://www.gmail.com</li>
-</ul>
-<p>Note the last one <b>is not</b> a link, as the source doesn&#8217;t include it in double-brackets and I don&#8217;t auto-recognize URLs.</p>
-<p>I should also handle links with <a href="http://www.xkcd.com">helpful text</a>.</p>
+<p class="title">Inline Formatting</p>
+<p>I want to make sure I handle all inline formatting. I need to handle <b>bold</b>, <i>italic</i>, <code>code</code>, <code>verbatim</code>, <span style="text-decoration:underline;">underline</span>, <del>strikethrough</del>.</p>
+<p>In addition, I need to make sure I can handle links. We&#8217;ve got simple links, like this:</p>
+<ul>
+  <li><a href="http://www.bing.com">http://www.bing.com</a></li>
+  <li><a href="http://www.google.com">http://www.google.com</a></li>
+  <li>http://www.gmail.com</li>
+</ul>
+<p>Note the last one <b>is not</b> a link, as the source doesn&#8217;t include it in double-brackets and I don&#8217;t auto-recognize URLs.</p>
+<p>I should also handle links with <a href="http://www.xkcd.com">helpful text</a>.</p>

data/spec/html_examples/inline-formatting.org

@@ -1,17 +1,17 @@
-Inline Formatting
-
-I want to make sure I handle all inline formatting. I need to handle
-*bold*, /italic/, =code=, ~verbatim~, _underline_, +strikethrough+. 
-
-In addition, I need to make sure I can handle links. We've got simple
-links, like this:
-
-- [[http://www.bing.com]]
-- [[http://www.google.com]]
-- http://www.gmail.com
-
-Note the last one *is not* a link, as the source doesn't include it in
-double-brackets and I don't auto-recognize URLs.
-
-I should also handle links with [[http://www.xkcd.com][helpful text]].
-
+Inline Formatting
+
+I want to make sure I handle all inline formatting. I need to handle
+*bold*, /italic/, =code=, ~verbatim~, _underline_, +strikethrough+. 
+
+In addition, I need to make sure I can handle links. We've got simple
+links, like this:
+
+- [[http://www.bing.com]]
+- [[http://www.google.com]]
+- http://www.gmail.com
+
+Note the last one *is not* a link, as the source doesn't include it in
+double-brackets and I don't auto-recognize URLs.
+
+I should also handle links with [[http://www.xkcd.com][helpful text]].
+

data/spec/html_examples/link-features.html

@@ -1,8 +1,8 @@
-<p class="title">link-features.org</p>
-<p>Org-mode export supports a lot of link features. I&#8217;ve covered &#8220;simple&#8221; HTML links elsewhere. Now let&#8217;s cover links to other org files, other sections within documents, etc.</p>
-<h1>Links to other org files</h1>
-<p>This is a link to the <code>code-comment.org</code> file in the same directory. In <code>emacs</code>, if you click it, the other file opens. We want the same behavior in the HTML export.</p>
-<p><a href="code-comment.html">Code Comment</a></p>
-<h1>Search links</h1>
-<p>This is a search link into code-comment.org.</p>
-<p><a href="code-comment.html">Code Comment</a></p>
+<p class="title">link-features.org</p>
+<p>Org-mode export supports a lot of link features. I&#8217;ve covered &#8220;simple&#8221; HTML links elsewhere. Now let&#8217;s cover links to other org files, other sections within documents, etc.</p>
+<h1>Links to other org files</h1>
+<p>This is a link to the <code>code-comment.org</code> file in the same directory. In <code>emacs</code>, if you click it, the other file opens. We want the same behavior in the HTML export.</p>
+<p><a href="code-comment.html">Code Comment</a></p>
+<h1>Search links</h1>
+<p>This is a search link into code-comment.org.</p>
+<p><a href="code-comment.html">Code Comment</a></p>

data/spec/html_examples/link-features.org

@@ -1,19 +1,19 @@
-#+TITLE: link-features.org
-
-Org-mode export supports a lot of link features. I've covered "simple"
-HTML links elsewhere. Now let's cover links to other org files, other
-sections within documents, etc.
-
-* Links to other org files
-
-  This is a link to the ~code-comment.org~ file in the same
-  directory. In ~emacs~, if you click it, the other file opens. We
-  want the same behavior in the HTML export.
-
-  [[file:code-comment.org][Code Comment]]
-
-* Search links
-
-  This is a search link into code-comment.org.
-
-  [[file:code-comment.org::*Code%20Comment][Code Comment]]
+#+TITLE: link-features.org
+
+Org-mode export supports a lot of link features. I've covered "simple"
+HTML links elsewhere. Now let's cover links to other org files, other
+sections within documents, etc.
+
+* Links to other org files
+
+  This is a link to the ~code-comment.org~ file in the same
+  directory. In ~emacs~, if you click it, the other file opens. We
+  want the same behavior in the HTML export.
+
+  [[file:code-comment.org][Code Comment]]
+
+* Search links
+
+  This is a search link into code-comment.org.
+
+  [[file:code-comment.org::*Code%20Comment][Code Comment]]

data/spec/html_examples/lists.html

@@ -1,19 +1,19 @@
-<h1 class="title">Lists</h1>
-<p>I want to make sure I have great support for lists.</p>
-<ul>
-  <li>This is an unordered list</li>
-  <li>This continues the unordered list</li>
-</ul>
-<p>And this is a paragraph <b>after</b> the list.</p>
-<h2>Wrapping within the list</h2>
-<ul>
-  <li>This is a single-line list item in the org file.</li>
-  <li>Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.</li>
-  <li>And this is the next item. The previous item needs to be on one line to keep <code>textile</code> happy.</li>
-  <li>Ditto the previous line, actually.</li>
-</ul>
-<h2>Edge cases</h2>
-<ul>
-  <li>This is a single-line list.</li>
-</ul>
-<p>And this is a <b>separate paragraph.</b> Note the indentation in the org file.</p>
+<h1 class="title">Lists</h1>
+<p>I want to make sure I have great support for lists.</p>
+<ul>
+  <li>This is an unordered list</li>
+  <li>This continues the unordered list</li>
+</ul>
+<p>And this is a paragraph <b>after</b> the list.</p>
+<h2>Wrapping within the list</h2>
+<ul>
+  <li>This is a single-line list item in the org file.</li>
+  <li>Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.</li>
+  <li>And this is the next item. The previous item needs to be on one line to keep <code>textile</code> happy.</li>
+  <li>Ditto the previous line, actually.</li>
+</ul>
+<h2>Edge cases</h2>
+<ul>
+  <li>This is a single-line list.</li>
+</ul>
+<p>And this is a <b>separate paragraph.</b> Note the indentation in the org file.</p>

data/spec/html_examples/lists.org

@@ -1,36 +1,36 @@
-* Lists
-
-I want to make sure I have great support for lists.
-
-- This is an unordered list
-- This continues the unordered list
-
-And this is a paragraph *after* the list.
-
-** Wrapping within the list
-
-   - This is a single-line list item in the org file.
-   - Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam
-     nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam
-     erat, sed diam voluptua. At vero eos et accusam et justo duo
-     dolores et ea rebum. Stet clita kasd gubergren, no sea takimata
-     sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit
-     amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor
-     invidunt ut labore et dolore magna aliquyam erat, sed diam
-     voluptua. At vero eos et accusam et justo duo dolores et ea
-     rebum. Stet clita kasd gubergren, no sea takimata sanctus est
-     Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet,
-     consetetur sadipscing elitr, sed diam nonumy eirmod tempor
-     invidunt ut labore et dolore magna aliquyam erat, sed diam
-     voluptua. At vero eos et accusam et justo duo dolores et ea
-     rebum. Stet clita kasd gubergren, no sea takimata sanctus est
-     Lorem ipsum dolor sit amet.
-   - And this is the next item. The previous item needs to be on one
-     line to keep =textile= happy.
-   - Ditto the previous line, actually.
-
-** Edge cases
-
-   - This is a single-line list.
-   And this is a *separate paragraph.* Note the indentation in the org
-   file.
+* Lists
+
+I want to make sure I have great support for lists.
+
+- This is an unordered list
+- This continues the unordered list
+
+And this is a paragraph *after* the list.
+
+** Wrapping within the list
+
+   - This is a single-line list item in the org file.
+   - Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam
+     nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam
+     erat, sed diam voluptua. At vero eos et accusam et justo duo
+     dolores et ea rebum. Stet clita kasd gubergren, no sea takimata
+     sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit
+     amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor
+     invidunt ut labore et dolore magna aliquyam erat, sed diam
+     voluptua. At vero eos et accusam et justo duo dolores et ea
+     rebum. Stet clita kasd gubergren, no sea takimata sanctus est
+     Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet,
+     consetetur sadipscing elitr, sed diam nonumy eirmod tempor
+     invidunt ut labore et dolore magna aliquyam erat, sed diam
+     voluptua. At vero eos et accusam et justo duo dolores et ea
+     rebum. Stet clita kasd gubergren, no sea takimata sanctus est
+     Lorem ipsum dolor sit amet.
+   - And this is the next item. The previous item needs to be on one
+     line to keep =textile= happy.
+   - Ditto the previous line, actually.
+
+** Edge cases
+
+   - This is a single-line list.
+   And this is a *separate paragraph.* Note the indentation in the org
+   file.

data/spec/html_examples/metadata-comment.html

@@ -1,27 +1,27 @@
-<h1 class="title">Metadata, etc.</h1>
-<p>I normally filter out things that look like metadata. Can&#8217;t do it any more. I need to see all of the following:</p>
-<pre class="example">
-* DONE Handle inline formatting
-  CLOSED: [2009-12-26 Sat 21:41]
-  :PROPERTIES:
-  :ARCHIVE_TIME: 2009-12-26 Sat 22:16
-  :ARCHIVE_FILE: ~/brians-brain/content/projects/orgmode_parser.org
-  :ARCHIVE_OLPATH: &lt;%= @page.title %&gt;/Future Development
-  :ARCHIVE_CATEGORY: orgmode_parser
-  :ARCHIVE_TODO: DONE
-  :END:
-
-  I still need to handle:
-
-  - [ ] =Inline code=
-
-  How does the =emacs= HTML parser handle *inline* formatting? Ah,
-  it looks like it defines everything in =org-emphasis-alist= (line
-  2855 of =org.el=).
-
-  And then look at =org-emphasis-regexp-components=, line 2828 of
-  =org.el=. It looks like they just use a crazy regexp for inline
-  formatting. Which is good, because it means I can copy!
-
-
-</pre>
+<h1 class="title">Metadata, etc.</h1>
+<p>I normally filter out things that look like metadata. Can&#8217;t do it any more. I need to see all of the following:</p>
+<pre class="example">
+* DONE Handle inline formatting
+  CLOSED: [2009-12-26 Sat 21:41]
+  :PROPERTIES:
+  :ARCHIVE_TIME: 2009-12-26 Sat 22:16
+  :ARCHIVE_FILE: ~/brians-brain/content/projects/orgmode_parser.org
+  :ARCHIVE_OLPATH: &lt;%= @page.title %&gt;/Future Development
+  :ARCHIVE_CATEGORY: orgmode_parser
+  :ARCHIVE_TODO: DONE
+  :END:
+
+  I still need to handle:
+
+  - [ ] =Inline code=
+
+  How does the =emacs= HTML parser handle *inline* formatting? Ah,
+  it looks like it defines everything in =org-emphasis-alist= (line
+  2855 of =org.el=).
+
+  And then look at =org-emphasis-regexp-components=, line 2828 of
+  =org.el=. It looks like they just use a crazy regexp for inline
+  formatting. Which is good, because it means I can copy!
+
+
+</pre>

data/spec/html_examples/metadata-comment.org

@@ -1,30 +1,30 @@
-* Metadata, etc.
-
-I normally filter out things that look like metadata. Can't do it any
-more. I need to see all of the following:
-
-#+BEGIN_EXAMPLE
-* DONE Handle inline formatting
-  CLOSED: [2009-12-26 Sat 21:41]
-  :PROPERTIES:
-  :ARCHIVE_TIME: 2009-12-26 Sat 22:16
-  :ARCHIVE_FILE: ~/brians-brain/content/projects/orgmode_parser.org
-  :ARCHIVE_OLPATH: <%= @page.title %>/Future Development
-  :ARCHIVE_CATEGORY: orgmode_parser
-  :ARCHIVE_TODO: DONE
-  :END:
-
-  I still need to handle:
-
-  - [ ] =Inline code=
-
-  How does the =emacs= HTML parser handle *inline* formatting? Ah,
-  it looks like it defines everything in =org-emphasis-alist= (line
-  2855 of =org.el=).
-
-  And then look at =org-emphasis-regexp-components=, line 2828 of
-  =org.el=. It looks like they just use a crazy regexp for inline
-  formatting. Which is good, because it means I can copy!
-
-
-#+END_EXAMPLE
+* Metadata, etc.
+
+I normally filter out things that look like metadata. Can't do it any
+more. I need to see all of the following:
+
+#+BEGIN_EXAMPLE
+* DONE Handle inline formatting
+  CLOSED: [2009-12-26 Sat 21:41]
+  :PROPERTIES:
+  :ARCHIVE_TIME: 2009-12-26 Sat 22:16
+  :ARCHIVE_FILE: ~/brians-brain/content/projects/orgmode_parser.org
+  :ARCHIVE_OLPATH: <%= @page.title %>/Future Development
+  :ARCHIVE_CATEGORY: orgmode_parser
+  :ARCHIVE_TODO: DONE
+  :END:
+
+  I still need to handle:
+
+  - [ ] =Inline code=
+
+  How does the =emacs= HTML parser handle *inline* formatting? Ah,
+  it looks like it defines everything in =org-emphasis-alist= (line
+  2855 of =org.el=).
+
+  And then look at =org-emphasis-regexp-components=, line 2828 of
+  =org.el=. It looks like they just use a crazy regexp for inline
+  formatting. Which is good, because it means I can copy!
+
+
+#+END_EXAMPLE

data/spec/html_examples/only-list.html

@@ -1,5 +1,5 @@
-<ul>
-  <li>This file has only a list</li>
-  <li>Note it will end with nothing other than a list item.</li>
-  <li>the world wants to know: Will org-ruby write the closing ul tag?</li>
-</ul>
+<ul>
+  <li>This file has only a list</li>
+  <li>Note it will end with nothing other than a list item.</li>
+  <li>the world wants to know: Will org-ruby write the closing ul tag?</li>
+</ul>

data/spec/html_examples/only-list.org

@@ -1,3 +1,3 @@
-- This file has only a list
-- Note it will end with nothing other than a list item.
-- the world wants to know: Will org-ruby write the closing ul tag?
+- This file has only a list
+- Note it will end with nothing other than a list item.
+- the world wants to know: Will org-ruby write the closing ul tag?

data/spec/html_examples/only-table.html

@@ -1,6 +1,6 @@
-<table>
-  <tr><th>One</th><th>Two</th><th>Three</th><th>Four</th></tr>
-  <tr><td>Five</td><td>Six</td><td>Seven</td><td>Eight</td></tr>
-  <tr><td>Nine</td><td>Ten</td><td>Eleven</td><td>Twelve</td></tr>
-  <tr><td><b>format</b></td><td><i>text</i></td><td><code>in</code></td><td><span style="text-decoration:underline;">cells</span></td></tr>
-</table>
+<table>
+  <tr><th>One</th><th>Two</th><th>Three</th><th>Four</th></tr>
+  <tr><td>Five</td><td>Six</td><td>Seven</td><td>Eight</td></tr>
+  <tr><td>Nine</td><td>Ten</td><td>Eleven</td><td>Twelve</td></tr>
+  <tr><td><b>format</b></td><td><i>text</i></td><td><code>in</code></td><td><span style="text-decoration:underline;">cells</span></td></tr>
+</table>

data/spec/html_examples/only-table.org

@@ -1,5 +1,5 @@
-| One      | Two    | Three  | Four    |
-|----------+--------+--------+---------|
-| Five     | Six    | Seven  | Eight   |
-| Nine     | Ten    | Eleven | Twelve  |
-| *format* | /text/ | ~in~   | _cells_ |
+| One      | Two    | Three  | Four    |
+|----------+--------+--------+---------|
+| Five     | Six    | Seven  | Eight   |
+| Nine     | Ten    | Eleven | Twelve  |
+| *format* | /text/ | ~in~   | _cells_ |

data/spec/html_examples/skip-header.html

@@ -1,3 +1,3 @@
-<p class="title">skip-header.org</p>
-<h1><span class="heading-number heading-number-1">1 </span>First heading</h1>
-<p>This should be the first text in the output.</p>
+<p class="title">skip-header.org</p>
+<h1><span class="heading-number heading-number-1">1 </span>First heading</h1>
+<p>This should be the first text in the output.</p>

data/spec/html_examples/skip-header.org

@@ -1,28 +1,28 @@
-#+TITLE:     skip-header.org
-#+AUTHOR:    
-#+EMAIL:     brian@BRIAN-DESK
-#+DATE:      2009-12-29 Tue
-#+DESCRIPTION: 
-#+KEYWORDS: 
-#+LANGUAGE:  en
-#+OPTIONS:   H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
-#+OPTIONS:   TeX:t LaTeX:nil skip:t d:nil todo:t pri:nil tags:not-in-toc
-#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
-#+EXPORT_SELECT_TAGS: export
-#+EXPORT_EXCLUDE_TAGS: noexport
-#+LINK_UP:   
-#+LINK_HOME: 
-This is header text.
-It exists in the org-file, but shouldn't show up in the HTML output.
-
-- Same with this list
-- Nope, shouldn't be in the output.
-
-#+BEGIN_EXAMPLE
-Even this code snippet shouldn't be there.
-Like a ninja. You can't see me.
-#+END_EXAMPLE
-
-* First heading
-
-  This should be the first text in the output.
+#+TITLE:     skip-header.org
+#+AUTHOR:    
+#+EMAIL:     brian@BRIAN-DESK
+#+DATE:      2009-12-29 Tue
+#+DESCRIPTION: 
+#+KEYWORDS: 
+#+LANGUAGE:  en
+#+OPTIONS:   H:3 num:t toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t
+#+OPTIONS:   TeX:t LaTeX:nil skip:t d:nil todo:t pri:nil tags:not-in-toc
+#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js
+#+EXPORT_SELECT_TAGS: export
+#+EXPORT_EXCLUDE_TAGS: noexport
+#+LINK_UP:   
+#+LINK_HOME: 
+This is header text.
+It exists in the org-file, but shouldn't show up in the HTML output.
+
+- Same with this list
+- Nope, shouldn't be in the output.
+
+#+BEGIN_EXAMPLE
+Even this code snippet shouldn't be there.
+Like a ninja. You can't see me.
+#+END_EXAMPLE
+
+* First heading
+
+  This should be the first text in the output.