github-markup 0.5.2 → 0.5.3
Sign up to get free protection for your applications and to get access to all the features.
- data/lib/github/markup/version.rb +1 -1
- data/lib/github/markups.rb +1 -1
- data/test/markups/README.mediawiki.html +3 -3
- metadata +4 -4
data/lib/github/markups.rb
CHANGED
|
@@ -19,7 +19,7 @@ markup(:creole, /creole/) do |content|
|
|
|
19
19
|
end
|
|
20
20
|
|
|
21
21
|
markup(:wikicloth, /mediawiki|wiki/) do |content|
|
|
22
|
-
WikiCloth::WikiCloth.new(
|
|
22
|
+
WikiCloth::WikiCloth.new(:data => content).to_html(:noedit => true)
|
|
23
23
|
end
|
|
24
24
|
|
|
25
25
|
command(:rest2html, /re?st(\.txt)?/)
|
|
@@ -9,12 +9,12 @@ Using Java from Ruby is JRuby's best-known feature---but you can also go in the
|
|
|
9
9
|
<table id="toc" class="toc" summary="Contents"><tr><td><div style="font-weight:bold">Table of Contents</div><ul></ul></td></tr></table>
|
|
10
10
|
|
|
11
11
|
</p><p>
|
|
12
|
-
<h1
|
|
12
|
+
<h1> <span class="mw-headline" id="Red_Bridge_JRuby_Embed">Red Bridge (JRuby Embed)</span></h1>
|
|
13
13
|
|
|
14
14
|
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="javascript:void(0)">legacy API</a> should still work, but we strongly recommend Red Bridge for all new projects.
|
|
15
15
|
|
|
16
16
|
</p><p>
|
|
17
|
-
<h2
|
|
17
|
+
<h2> <span class="mw-headline" id="Features_of_Red_Bridge">Features of Red Bridge</span></h2>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">JSR223</a> and <a href="http://jakarta.apache.org/bsf/">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.
|
|
18
18
|
|
|
19
19
|
</p><p>
|
|
20
20
|
Which API should you use? For projects where Ruby is the only scripting language involved, we recommend Embed Core for the following reasons:
|
|
@@ -31,5 +31,5 @@ Which API should you use? For projects where Ruby is the only scripting language
|
|
|
31
31
|
The full <a href="http://jruby-embed.kenai.com/docs/">API documentation</a> has all the gory details. It's worth talking about a couple of the finer points here.
|
|
32
32
|
|
|
33
33
|
</p><p>
|
|
34
|
-
<h1
|
|
34
|
+
<h1> <span class="mw-headline" id="Previous_Embedding_JRuby_Page">Previous Embedding JRuby Page</span></h1>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="javascript:void(0)">legacy embedding</a> page.
|
|
35
35
|
</p>
|
metadata
CHANGED
|
@@ -1,13 +1,13 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: github-markup
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
hash:
|
|
4
|
+
hash: 13
|
|
5
5
|
prerelease: false
|
|
6
6
|
segments:
|
|
7
7
|
- 0
|
|
8
8
|
- 5
|
|
9
|
-
-
|
|
10
|
-
version: 0.5.
|
|
9
|
+
- 3
|
|
10
|
+
version: 0.5.3
|
|
11
11
|
platform: ruby
|
|
12
12
|
authors:
|
|
13
13
|
- Chris Wanstrath
|
|
@@ -15,7 +15,7 @@ autorequire:
|
|
|
15
15
|
bindir: bin
|
|
16
16
|
cert_chain: []
|
|
17
17
|
|
|
18
|
-
date:
|
|
18
|
+
date: 2011-01-03 00:00:00 -08:00
|
|
19
19
|
default_executable:
|
|
20
20
|
dependencies: []
|
|
21
21
|
|