gitlab-markup 1.5.0.pre

data/test/markups/README.asciidoc

@@ -0,0 +1,23 @@
+= Document Title
+
+== First Section
+
+* One
+* Two
+
+Refer to <<another-section>> or <<another-section-1>>.
+
+== Another Section
+
+NOTE: Here is some source code.
+
+```ruby
+puts "Hello, World!"
+```
+
+* [ ] todo
+* [x] done
+
+== Another Section
+
+content

data/test/markups/README.asciidoc.html

@@ -0,0 +1,59 @@
+<h1>Document Title</h1>
+<div>
+<h2>First Section</h2>
+<div>
+<div>
+<ul>
+<li>
+<p>One</p>
+</li>
+<li>
+<p>Two</p>
+</li>
+</ul>
+</div>
+<div>
+<p>Refer to <a href="#another-section">Another Section</a> or <a href="#another-section-1">Another Section</a>.</p>
+</div>
+</div>
+</div>
+<div>
+<h2>Another Section</h2>
+<div>
+<div>
+<table>
+<tr>
+<td>
+<div>Note</div>
+</td>
+<td>
+Here is some source code.
+</td>
+</tr>
+</table>
+</div>
+<div>
+<div>
+<pre lang="ruby"><code>puts "Hello, World!"</code></pre>
+</div>
+</div>
+<div>
+<ul>
+<li>
+<p>❏ todo</p>
+</li>
+<li>
+<p>✓ done</p>
+</li>
+</ul>
+</div>
+</div>
+</div>
+<div>
+<h2>Another Section</h2>
+<div>
+<div>
+<p>content</p>
+</div>
+</div>
+</div>

data/test/markups/README.creole

@@ -0,0 +1,34 @@
+= H1 =
+
+== H2 ==
+
+paragraph of text that will be turned into a paragraph element. It can
+go over several lines with line breaks, it will be turned into a
+contiguous paragraph element.
+
+You can force a linebreak in your paragraph text\\thusly.
+
+
+ * a list element
+ ** sub list element
+ * 2nd list element
+
+{{{
+pre formatted text
+
+$ ls -la
+total 56
+drwxr-xr-x   6 nferrier users  4096 Jul  5 23:10 .
+drwxr-x--- 120 nferrier users 12288 Jul  5 19:36 ..
+drwxr-xr-x   2 nferrier users  4096 Jul  5 18:19 bin
+-rw-r--r--   1 nferrier users     6 Jul  5 18:19 .gitignore
+drwxr-xr-x   4 nferrier users  4096 Jul  5 23:10 .hg
+-rw-r--r--   1 nferrier users  1182 Jul  5 18:19 HISTORY.md
+-rw-r--r--   1 nferrier users   562 Jul  5 18:19 .kick
+drwxr-xr-x   3 nferrier users  4096 Jul  5 18:19 lib
+-rw-r--r--   1 nferrier users  1050 Jul  5 18:19 LICENSE
+-rw-r--r--   1 nferrier users  1312 Jul  5 18:19 Rakefile
+-rw-r--r--   1 nferrier users  3390 Jul  5 18:19 README.md
+drwxr-xr-x   3 nferrier users  4096 Jul  5 18:19 test
+}}}
+

data/test/markups/README.creole.html

@@ -0,0 +1,20 @@
+<h1>H1</h1><h2>H2</h2><p>paragraph of text that will be turned into a paragraph element. It can go over several lines with line breaks, it will be turned into a contiguous paragraph element.</p><p>You can force a linebreak in your paragraph text<br>thusly.</p><ul>
+<li>a list element<ul><li>sub list element</li></ul>
+</li>
+<li>2nd list element</li>
+</ul><pre>pre formatted text
+
+$ ls -la
+total 56
+drwxr-xr-x   6 nferrier users  4096 Jul  5 23:10 .
+drwxr-x--- 120 nferrier users 12288 Jul  5 19:36 ..
+drwxr-xr-x   2 nferrier users  4096 Jul  5 18:19 bin
+-rw-r--r--   1 nferrier users     6 Jul  5 18:19 .gitignore
+drwxr-xr-x   4 nferrier users  4096 Jul  5 23:10 .hg
+-rw-r--r--   1 nferrier users  1182 Jul  5 18:19 HISTORY.md
+-rw-r--r--   1 nferrier users   562 Jul  5 18:19 .kick
+drwxr-xr-x   3 nferrier users  4096 Jul  5 18:19 lib
+-rw-r--r--   1 nferrier users  1050 Jul  5 18:19 LICENSE
+-rw-r--r--   1 nferrier users  1312 Jul  5 18:19 Rakefile
+-rw-r--r--   1 nferrier users  3390 Jul  5 18:19 README.md
+drwxr-xr-x   3 nferrier users  4096 Jul  5 18:19 test</pre>

data/test/markups/README.litcoffee

@@ -0,0 +1,59 @@
+Literate CoffeeScript Test
+--------------------------
+
+> Taken from https://github.com/jashkenas/coffee-script/blob/master/test/literate.litcoffee
+
+comment comment
+
+    test "basic literate CoffeeScript parsing", ->
+      ok yes
+
+now with a...
+
+    test "broken up indentation", ->
+
+... broken up ...
+
+      do ->
+
+... nested block.
+
+        ok yes
+
+Code must be separated from text by a blank line.
+
+    test "code blocks must be preceded by a blank line", ->
+
+The next line is part of the text and will not be executed.
+      fail()
+
+      ok yes
+
+Code in `backticks is not parsed` and...
+
+    test "comments in indented blocks work", ->
+      do ->
+        do ->
+          # Regular comment.
+
+          ###
+            Block comment.
+          ###
+
+          ok yes
+
+Regular [Markdown](http://example.com/markdown) features,
+like links and unordered lists, are fine:
+
+  * I
+
+  * Am
+
+  * A
+
+  * List
+
+Tabs work too:
+
+  test "tabbed code", ->
+    ok yes

data/test/markups/README.litcoffee.html

@@ -0,0 +1,66 @@
+<h2>Literate CoffeeScript Test</h2>
+
+<blockquote>
+<p>Taken from https://github.com/jashkenas/coffee-script/blob/master/test/literate.litcoffee</p>
+</blockquote>
+
+<p>comment comment</p>
+
+<pre><code>test "basic literate CoffeeScript parsing", -&gt;
+  ok yes
+</code></pre>
+
+<p>now with a...</p>
+
+<pre><code>test "broken up indentation", -&gt;
+</code></pre>
+
+<p>... broken up ...</p>
+
+<pre><code>  do -&gt;
+</code></pre>
+
+<p>... nested block.</p>
+
+<pre><code>    ok yes
+</code></pre>
+
+<p>Code must be separated from text by a blank line.</p>
+
+<pre><code>test "code blocks must be preceded by a blank line", -&gt;
+</code></pre>
+
+<p>The next line is part of the text and will not be executed.
+      fail()</p>
+
+<pre><code>  ok yes
+</code></pre>
+
+<p>Code in <code>backticks is not parsed</code> and...</p>
+
+<pre><code>test "comments in indented blocks work", -&gt;
+  do -&gt;
+    do -&gt;
+      # Regular comment.
+
+      ###
+        Block comment.
+      ###
+
+      ok yes
+</code></pre>
+
+<p>Regular <a href="http://example.com/markdown">Markdown</a> features,
+like links and unordered lists, are fine:</p>
+
+<ul>
+<li><p>I</p></li>
+<li><p>Am</p></li>
+<li><p>A</p></li>
+<li><p>List</p></li>
+</ul>
+
+<p>Tabs work too:</p>
+
+<p>test "tabbed code", -&gt;
+    ok yes</p>

data/test/markups/README.markdown

@@ -0,0 +1,2 @@
+* One
+* Two

data/test/markups/README.markdown.html

@@ -0,0 +1,4 @@
+<ul>
+<li>One</li>
+<li>Two</li>
+</ul>

data/test/markups/README.mediawiki

@@ -0,0 +1,30 @@
+[[Home|» JRuby Project Wiki Home Page]]
+<h1>Embedding JRuby</h1>
+Using Java from Ruby is JRuby's best-known feature---but you can also go in the other direction, and use Ruby from Java.  There are several different ways to do this. You can execute entire Ruby scripts, call individual Ruby methods, or even implement a Java interface in Ruby (thus allowing you to treat Ruby objects like Java ones).  We refer to all these techniques generically as "embedding."  This section will explain how to embed JRuby in your Java project.
+
+__TOC__
+
+= Red Bridge (JRuby Embed) =
+
+<tt>one-<two</tt>
+<pre>a-b</pre>
+
+JRuby has long had a private embedding API, which was closely tied to the runtime's internals and therefore changed frequently as JRuby evolved. Since version 1.4, however, we have also provided a more stable public API, known as Red Bridge or JRuby Embed. Existing Java programs written to the [[DirectJRubyEmbedding|legacy API]] should still work, but we strongly recommend Red Bridge for all new projects.
+
+== Features of Red Bridge ==
+Red Bridge consists of two layers: Embed Core on the bottom, and implementations of [http://www.jcp.org/en/jsr/detail?id=223 JSR223] and [http://jakarta.apache.org/bsf/ BSF] on top. Embed Core is JRuby-specific, and can take advantage of much of JRuby's power. JSR223 and BSF are more general interfaces that provide a common ground across scripting languages.
+
+Which API should you use? For projects where Ruby is the only scripting language involved, we recommend Embed Core for the following reasons:
+
+# With Embed Core, you can create several Ruby environments in one JVM, and configure them individually (via <code>org.jruby.RubyInstanceConfig</code>. With the other APIs, configuration options can only be set globally, via the <code>System</code> properties.
+# Embed Core offers several shortcuts, such as loading scripts from a <code>java.io.InputStream</code>, or returning Java-friendly objects from Ruby code. These allow you to skip a lot of boilerplate.
+
+For projects requiring multiple scripting languages, JSR223 is a good fit. Though the API is language-independent, JRuby's implementation of it allows you to set some Ruby-specific options. In particular, you can control the threading model of the scripting engine, the lifetime of local variables, compilation mode, and how line numbers are displayed.
+
+The full [http://jruby-embed.kenai.com/docs/ API documentation] has all the gory details. It's worth talking about a couple of the finer points here.
+
+= Previous Embedding JRuby Page=
+We recommend using Embed Core; however, if you're maintaining code that uses the old API, you can find its documentation on the [[JavaIntegration|legacy embedding]]<ref>This link goes nowhere.</ref> page.
+
+= References =
+<references/>

data/test/markups/README.mediawiki.html

@@ -0,0 +1,60 @@
+<p><a href="Home">» JRuby Project Wiki Home Page</a>
+</p><h1>Embedding JRuby</h1>
+Using Java from Ruby is JRuby's best-known feature---but you can also go in the other direction, and use Ruby from Java.  There are several different ways to do this. You can execute entire Ruby scripts, call individual Ruby methods, or even implement a Java interface in Ruby (thus allowing you to treat Ruby objects like Java ones).  We refer to all these techniques generically as "embedding."  This section will explain how to embed JRuby in your Java project.
+
+<p></p><table summary="Contents"><tr><td>
+<div><h2>Table of Contents</h2></div>
+<ul>
+<li>
+<a href="#Red_Bridge_JRuby_Embed">Red Bridge (JRuby Embed)</a><ul><li><a href="#Features_of_Red_Bridge">Features of Red Bridge</a></li></ul>
+</li>
+<li><a href="#Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</a></li>
+<li><a href="#References">References</a></li>
+</ul>
+</td></tr></table>
+
+
+<h1>
+<a name="Red_Bridge_JRuby_Embed"></a>Red Bridge (JRuby Embed)</h1>
+
+
+<p><tt>one-&lt;two</tt>
+</p><pre>a-b</pre>
+
+
+<p>JRuby has long had a private embedding API, which was closely tied to the runtime's internals and therefore changed frequently as JRuby evolved. Since version 1.4, however, we have also provided a more stable public API, known as Red Bridge or JRuby Embed. Existing Java programs written to the <a href="DirectJRubyEmbedding">legacy API</a> should still work, but we strongly recommend Red Bridge for all new projects.
+</p>
+
+<h2>
+<a name="Features_of_Red_Bridge"></a>Features of Red Bridge</h2>
+
+
+<p>Red Bridge consists of two layers: Embed Core on the bottom, and implementations of <a href="http://www.jcp.org/en/jsr/detail?id=223" target="_blank">JSR223</a> and <a href="http://jakarta.apache.org/bsf/" target="_blank">BSF</a> on top. Embed Core is JRuby-specific, and can take advantage of much of JRuby's power. JSR223 and BSF are more general interfaces that provide a common ground across scripting languages.
+</p>
+<p>Which API should you use? For projects where Ruby is the only scripting language involved, we recommend Embed Core for the following reasons:
+</p>
+
+
+
+<p></p><ol>
+<li>With Embed Core, you can create several Ruby environments in one JVM, and configure them individually (via <code>org.jruby.RubyInstanceConfig</code>. With the other APIs, configuration options can only be set globally, via the <code>System</code> properties.</li>
+<li>Embed Core offers several shortcuts, such as loading scripts from a <code>java.io.InputStream</code>, or returning Java-friendly objects from Ruby code. These allow you to skip a lot of boilerplate.</li>
+</ol>
+For projects requiring multiple scripting languages, JSR223 is a good fit. Though the API is language-independent, JRuby's implementation of it allows you to set some Ruby-specific options. In particular, you can control the threading model of the scripting engine, the lifetime of local variables, compilation mode, and how line numbers are displayed.
+
+<p>The full <a href="http://jruby-embed.kenai.com/docs/" target="_blank">API documentation</a> has all the gory details. It's worth talking about a couple of the finer points here.
+</p>
+
+<h1>
+<a name="Previous_Embedding_JRuby_Page"></a>Previous Embedding JRuby Page</h1>
+
+
+<p>We recommend using Embed Core; however, if you're maintaining code that uses the old API, you can find its documentation on the <a href="JavaIntegration">legacy embedding</a><sup>[<a href="#cite_note-1">1</a>]</sup> page.
+</p>
+
+<h1>
+<a name="References"></a>References</h1>
+
+
+<p></p><ol><li>
+<b><a href="#cite_ref-1-0">^</a> </b> This link goes nowhere.</li></ol>

data/test/markups/README.noformat

@@ -0,0 +1,2 @@
+* One
+* Two

data/test/markups/README.noformat.html

@@ -0,0 +1,2 @@
+* One
+* Two

data/test/markups/README.org

@@ -0,0 +1,131 @@
+#+TITLE:     org-ruby
+#+AUTHOR:    Brian Dewey
+#+EMAIL:     bdewey@gmail.com
+#+DATE:      2009-12-21
+#+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:nil d:nil todo:nil pri:nil tags:not-in-toc
+#+EXPORT_EXCLUDE_TAGS: exclude
+#+STARTUP:    showall
+
+ | Status:   | Under Development                 |
+ | Location: | [[http://github.com/wallyqs/org-ruby]] |
+ | Version:  | 0.9.0                             |
+
+* Description
+
+  Helpful Ruby routines for parsing orgmode files. The most
+  significant thing this library does today is convert orgmode files
+  to textile. Currently, you cannot do much to customize the
+  conversion. The supplied textile conversion is optimized for
+  extracting "content" from the orgfile as opposed to "metadata."
+
+* History
+
+** 2014-02-08: Version 0.9.0
+
+   - Let's make sure =#+INCLUDE:= is not supported
+
+#+INCLUDE: "./README.txt" src text
+
+   - And confirm that syntax highlight is supported
+
+#+begin_src ruby
+module GitHub
+  module Markup
+    VERSION = 'test'
+    Version = VERSION
+  end
+end
+#+end_src
+
+** 2009-12-30: Version 0.5.1
+
+   - Minor enhancement: Recognize lines starting with ":" as examples.
+   - Minor enhancement: Recognize #+BEGIN_SRC as source blocks
+   - Minor enhancement: Add "src" and "example" classes to <pre> blocks.
+
+
+** 2009-12-30: Version 0.5.0
+
+   - Parse (but not necessarily *use*) in-buffer settings. The following
+     in-buffer settings *are* used:
+     - Understand the #+TITLE: directive.
+     - Exporting todo keywords (option todo:t)
+     - Numbering headlines (option num:t)
+     - Skipping text before the first headline (option skip:t)
+     - Skipping tables (option |:nil)
+     - Custom todo keywords
+     - EXPORT_SELECT_TAGS and EXPORT_EXLUDE_TAGS for controlling parts of
+       the tree to export
+   - Rewrite "file:(blah).org" links to "http:(blah).html" links. This
+     makes the inter-links to other org-mode files work.
+   - Uses <th> tags inside table rows that precede table separators.
+   - Bugfixes:
+     - Headings now have HTML escaped.
+
+** 2009-12-29: Version 0.4.2
+
+   - Got rid of the extraneous newline at the start of code blocks.
+   - Everything now shows up in code blocks, even org-mode metadata.
+   - Fixed bugs:
+     - Regressed smart double quotes with HTML escaping. Added a test
+       case and fixed the regression.
+
+** 2009-12-29: Version 0.4.1
+   - HTML is now escaped by default
+   - org-mode comments will show up in a code block.
+
+** 2009-12-29: Version 0.4
+
+   - The first thing output in HTML gets the class "title"
+   - HTML output is now indented
+   - Proper support for multi-paragraph list items.
+
+     See? This paragraph is part of the last bullet.
+     
+   - Fixed bugs:
+     - "rake spec" wouldn't work on Linux. Needed "require 'rubygems'".
+
+** 2009-12-27: Version 0.3
+
+   - Uses rubypants to get better typography (smart quotes, elipses, etc...).
+   - Fixed bugs:
+     - Tables and lists did not get properly closed at the end of file
+     - You couldn't do inline formatting inside table cells
+     - Characters in PRE blocks were not HTML escaped.
+   
+** 2009-12-26: Version 0.2
+
+   - Added =to_html= output on the parser.
+   - Added support for the full range of inline markup: *bold*,
+     /italic/, =code=, ~verbatim~, _underline_, +strikethrough+.
+   - Lots of refactoring to make the code more maintainable.
+
+** 2009-12-23: Version 0.1
+
+   - Added support for block code, like this:
+
+     #+BEGIN_EXAMPLE
+     def flush!
+     @logger.debug "FLUSH ==========> #{@output_type}"
+     if (@output_type == :blank) then
+       @output << "\n"
+     elsif (@buffer.length > 0) then
+       if @cancel_modifier then
+         @output << "p. " if @output_type == :paragraph
+         @cancel_modifier = false
+       end
+       @output << @paragraph_modifier if (@paragraph_modifier and not sticky_modifier?)
+       @output << @buffer.textile_substitution << "\n"
+     end
+     @buffer = ""
+   end
+   #+END_EXAMPLE
+
+   - Major code cleanup: Created the =OutputBuffer= class that
+     greatly simplified a lot of the messiness of =textile=
+     conversion.
+   - Added support for line breaks within list items.