ronn-ng 0.9.0 → 0.9.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: caef2e245387dc095c174fe0db641e9548708a7e4ed06bbbbb5744ecec946a6c
-  data.tar.gz: ed1bf5365df919a3e346f666956f0dc1419e3854e5114ec364a21853bdb8559a
+  metadata.gz: a0c86d52512fedd7a5b3b61f1867851fcab7877706e458f4cde45e073df6fa4a
+  data.tar.gz: 18d7a1560428cf229e72956656ddc0395bae82ca6a3824bd75b116b44e437be2
 SHA512:
-  metadata.gz: d00d492c752114c195f233b382820350c6048280a833324ae5a74b97bf79e581c64a4764cd808a7b8996ca73cc2cc7d7ffe6232dea500efbdb7cf3ccc59cfd59
-  data.tar.gz: 3a01bfda55e74743e125a036e5397b0fe32464386a9e6983469d64422ceaa915934b812735c7cdf1f082241fe0cae3b13bb793121eb375005e2972a57a8fc1d0
+  metadata.gz: 4578b4612b2c004a2aa06f27161008fd57c7ee70e3715f3da8a9872e0c023f91d45651f65c75e358bfcd79712f4870e5e63c27f63bbf5614688010dfa2fae5c3
+  data.tar.gz: e180ee66f3bca9a20fe5e99ac8b47ce1d69fb5bbc65f40a95bab9500f5c0efe6a65dc2a225edf5df972b32ccf17b30773a31f8cc19104eab5192aa85fd807e08

data/CHANGES

@@ -1,6 +1,11 @@
 Ronn-NG CHANGES
 ===============
 
+Version 0.9.1 (2020 Apr 09)
+---------------------------
+
+* Fix underlining issue (https://github.com/apjanke/ronn-ng/pull/41)
+
 Version 0.9.0 (2019 Dec 21)
 ---------------------------
 

data/bin/ronn

@@ -31,12 +31,19 @@
 # /   -W                        disable previously enabled troff warnings
 # /       --version             show ronn version and exit
 # /       --help                show this help message
+# /   -E <encoding>             specify the encoding files are in (default is UTF-8)
+# /                             Note: this only affects files. Data passed in to ronn's STDIN
+# /                             must be in UTF-8 regardless of the -E setting.
 # /
 # / A <file> named example.1.ronn generates example.1.html (HTML manpage)
 # / and example.1 (roff manpage) by default.
 require 'date'
 require 'optparse'
 
+# Ronn wants its inputs to be in UTF-8, regardless of the user's
+# locale settings or Ruby version.
+Encoding.default_external = Encoding::UTF_8
+
 def usage
   puts File.readlines(__FILE__)
            .grep(/^# \/.*/)
@@ -75,6 +82,7 @@ view    = false
 server  = false
 port_arg = nil
 formats = nil
+encoding = 'UTF-8'
 options = {}
 write_index = false
 styles = %w[man]
@@ -111,9 +119,10 @@ ARGV.options do |argv|
   argv.on('-f', '--fragment') { (formats ||= []) << 'html_fragment' }
   argv.on('--markdown')       { (formats ||= []) << 'markdown' }
   argv.on('--yaml')           { (formats ||= []) << 'yaml' }
+  argv.on('-E', '--encoding=V') { |val| encoding = val }
 
   # html output options
-  argv.on('-s', '--style=V')  { |val| styles += val.split(/[, \n]+/) }
+  argv.on('-s', '--style=V') { |val| styles += val.split(/[, \n]+/) }
 
   # manual attribute options
   %w[name section manual organization date].each do |attribute|
@@ -158,6 +167,7 @@ formats.delete('html') if formats.include?('html_fragment')
 options['date'] &&= Date.strptime(options['date'], '%Y-%m-%d')
 options['styles'] = styles
 options['outdir'] = output_dir
+options['encoding'] = encoding
 
 unless port_arg.nil?
   begin

data/lib/ronn.rb

@@ -42,6 +42,6 @@ module Ronn
   # value generated by: rake rev
   # or edit manually; I'm not sure of how rake rev interacts with git
   # tags -apjanke
-  REV = '0.9.0'.freeze
+  REV = '0.9.1'.freeze
   VERSION = version
 end

data/lib/ronn/document.rb

@@ -23,6 +23,9 @@ module Ronn
     # object is created with a stream, in which case stdin will be read.
     attr_reader :path
 
+    # Encoding that the Ronn document is in
+    attr_accessor :encoding
+
     # The raw input data, read from path or stream and unmodified.
     attr_reader :data
 
@@ -73,7 +76,7 @@ module Ronn
                   if ['-', nil].include?(f)
                     STDIN.read
                   else
-                    File.read(f)
+                    File.read(f, encoding: @encoding)
                   end
                 end
       @data = @reader.call(path)

data/lib/ronn/roff.rb

@@ -281,13 +281,13 @@ module Ronn
             inline_filter(node.children)
           elsif node.has_attribute?('data-bare-link')
             write '\fI'
-            write '\%' + escape(node.attributes['href'].content)
+            inline_filter(node.children)
             write '\fR'
           else
             inline_filter(node.children)
             write ' '
             write '\fI'
-            write '\%' + escape(node.attributes['href'].content)
+            write escape(node.attributes['href'].content)
             write '\fR'
           end
 

data/man/ronn-format.7

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.9.0
-.\" http://github.com/apjanke/ronn-ng/tree/0.9.0
-.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.9.0" "Ronn Manual"
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.9.1" "Ronn Manual"
 .SH "NAME"
 \fBronn\-format\fR \- manual authoring format based on Markdown
 .SH "SYNOPSIS"

data/man/ronn.1

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.9.0
-.\" http://github.com/apjanke/ronn-ng/tree/0.9.0
-.TH "RONN" "1" "December 2019" "Ronn-NG 0.9.0" "Ronn Manual"
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "RONN" "1" "January 2020" "Ronn-NG 0.9.1" "Ronn Manual"
 .SH "NAME"
 \fBronn\fR \- convert markdown files to manpages
 .SH "SYNOPSIS"
@@ -13,6 +13,8 @@
 \fBronn\fR \fB\-\-pipe\fR \fIfile\fR
 .br
 \fBronn\fR < \fIfile\fR
+.br
+\fBronn\fR \fB\-E\fR|\fB\-\-encoding\fR \fIencoding\fR \|\.\|\.\|\.
 .SH "DESCRIPTION"
 \fBRonn\fR converts textfiles to standard roff\-formatted Unix manpages or HTML\. ronn\-format(7) is based on markdown(7) but includes additional rules and syntax geared toward authoring manuals\.
 .P
@@ -24,13 +26,15 @@ With no \fIfile\fR arguments, \fBronn\fR acts as simple filter\. Ronn source tex
 .SH "FILES"
 The \fBronn\fR command expects input to be valid ronn\-format(7) text\. Source files are typically named \fIname\fR\.\fIsection\fR\.ronn (e\.g\., \fBexample\.1\.ronn\fR)\. The \fIname\fR and \fIsection\fR should match the name and section defined in the \fIfile\fR\'s heading\.
 .P
+Source files must be in UTF\-8 encoding, or the encoding specified by the \fB\-E\fR/\fB\-\-encoding\fR option, regardless of the locale that \fBronn\fR is running under\.
+.P
 When building roff or HTML output files, destination filenames are determined by taking the basename of the input \fIfile\fR and adding the appropriate file extension (or removing the file extension in the case of roff output)\. For example, executing \fBronn example\.1\.ronn\fR generates \fBexample\.1\fR with roff output and \fBexample\.1\.html\fR with HTML output\.
 .SH "OPTIONS"
 These options control whether output is written to file(s), standard output, or directly to a man pager\.
 .IP "\[ci]" 4
 \fB\-m\fR, \fB\-\-man\fR: Don\'t generate files, display \fIfile\fRs as if man(1) were invoked on the roff output file\. This simulates default man behavior by piping the roff output through groff(1) and the paging program specified by the \fBMANPAGER\fR environment variable\.
 .IP "\[ci]" 4
-\fB\-S\fR, \fB\-\-server\fR: Don\'t generate files, start an HTTP server at \fI\%http://localhost:1207/\fR and serve dynamically generated HTML for the set of input \fIfile\fRs\. A file named \fIexample\.2\.ronn\fR is served as \fI/example\.2\.html\fR\. There\'s also an index page at the root with links to each \fIfile\fR\.
+\fB\-S\fR, \fB\-\-server\fR: Don\'t generate files, start an HTTP server at \fIhttp://localhost:1207/\fR and serve dynamically generated HTML for the set of input \fIfile\fRs\. A file named \fIexample\.2\.ronn\fR is served as \fI/example\.2\.html\fR\. There\'s also an index page at the root with links to each \fIfile\fR\.
 .IP
 The server respects the \fB\-\-style\fR and document attribute options (\fB\-\-manual\fR, \fB\-\-date\fR, etc\.)\. These same options can be varied at request time by giving them as query parameters: \fB?manual=FOO&style=dark,toc\fR
 .IP
@@ -41,6 +45,8 @@ The server respects the \fB\-\-style\fR and document attribute options (\fB\-\-m
 \fB\-\-pipe\fR: Don\'t generate files, write generated output to standard output\. This is the default behavior when ronn source text is piped in on standard input and no \fIfile\fR arguments are provided\.
 .IP "\[ci]" 4
 \fB\-o\fR=\fIdirectory\fR, \fB\-\-output\-dir\fR=\fIdirectory\fR: Write generated files to the specified directory instead of the default location\.
+.IP "\[ci]" 4
+\fB\-E\fR=\fIencoding\fR, \fB\-\-encoding\fR=<encoding: Specify the encoding that input files are in\. Default is UTF\-8, regardless of user\'s locale settings\. Input sent to STDIN is always treated as UTF\-8, regardless of whether \fB\-E\fR is passed\.
 .IP "" 0
 .P
 Format options control the files \fBronn\fR generates, or the output format when the \fB\-\-pipe\fR argument is specified\. When no format options are given, both \fB\-\-roff\fR and \fB\-\-html\fR are assumed\.
@@ -54,7 +60,7 @@ Generate output in HTML format\.
 \fB\-f\fR, \fB\-\-fragment\fR
 Generate output in HTML format but only the document fragment, not the header, title, or footer\.
 .P
-Document attributes displayed in the header and footer areas of generated content are specified with these options\. (These values may also be set via the \fI\%#ENVIRONMENT\fR\.)
+Document attributes displayed in the header and footer areas of generated content are specified with these options\. (These values may also be set via the \fIENVIRONMENT\fR\.)
 .TP
 \fB\-\-manual\fR=\fImanual\fR
 The name of the manual this man page belongs to; \fImanual\fR is prominently displayed top\-center in the header area\.
@@ -70,11 +76,11 @@ HTML output can be customized through the use of CSS stylesheets:
 \fB\-\-style\fR=\fImodule\fR[,\fImodule\fR]\|\.\|\.\|\.
 The list of CSS stylesheets to apply to the document\. Multiple \fImodule\fR arguments may be specified, but must be separated by commas or spaces\.
 .IP
-When \fImodule\fR is a simple word, search for files named \fImodule\fR\fB\.css\fR in all directories listed in the \fI\%#ENVIRONMENT\fR environment variable, and then search internal styles\.
+When \fImodule\fR is a simple word, search for files named \fImodule\fR\fB\.css\fR in all directories listed in the \fI\fBRONN_STYLE\fR\fR environment variable, and then search internal styles\.
 .IP
 When \fImodule\fR includes a \fI/\fR character, use it as the full path to a stylesheet file\.
 .IP
-Internal styles are \fIman\fR (included by default), \fItoc\fR, and \fI80c\fR\. See \fI\%#STYLES\fR for descriptions of features added by each module\.
+Internal styles are \fIman\fR (included by default), \fItoc\fR, and \fI80c\fR\. See \fISTYLES\fR for descriptions of features added by each module\.
 .P
 Miscellaneous options:
 .TP
@@ -143,7 +149,7 @@ The heading and footing, respectively\.
 \fB\.man\-title\fR
 The main \fB<h1>\fR element\. Hidden by default unless the manual has no \fIname\fR or \fIsection\fR attributes\.
 .P
-See the builtin style sources \fI\%http://github\.com/apjanke/ronn\-ng/tree/master/lib/ronn/template\fR for examples\.
+See the builtin style sources \fIhttp://github\.com/apjanke/ronn\-ng/tree/master/lib/ronn/template\fR for examples\.
 .SH "EXAMPLES"
 Build roff and HTML output files and view the roff manpage using man(1):
 .IP "" 4
@@ -189,7 +195,7 @@ $ ronn \-\-man hello\.1\.ronn
 .fi
 .IP "" 0
 .P
-Serve HTML manpages at \fI\%http://localhost:1207/\fR for all \fB*\.ronn\fR files under a \fBman/\fR directory:
+Serve HTML manpages at \fIhttp://localhost:1207/\fR for all \fB*\.ronn\fR files under a \fBman/\fR directory:
 .IP "" 4
 .nf
 $ ronn \-\-server man/*\.ronn
@@ -216,6 +222,6 @@ The paging program used for man pages\. This is typically set to something like
 \fBPAGER\fR
 Used instead of \fBMANPAGER\fR when \fBMANPAGER\fR is not defined\.
 .SH "COPYRIGHT"
-Ronn\-NG is Copyright (C) 2009 Ryan Tomayko \fI\%http://tomayko\.com/about\fR and (C) 2018 Andrew Janke \fI\%https://apjanke\.net\fR
+Ronn\-NG is Copyright (C) 2009 Ryan Tomayko \fIhttp://tomayko\.com/about\fR and (C) 2018 Andrew Janke \fIhttps://apjanke\.net\fR
 .SH "SEE ALSO"
 groff(1), man(1), pandoc(1), manpages(5), markdown(7), roff(7), ronn\-format(7)

data/man/ronn.1.ronn

@@ -7,7 +7,8 @@ ronn(1) -- convert markdown files to manpages
 `ronn` `-m`|`--man` <file>...<br>
 `ronn` `-S`|`--server` <file>...<br>
 `ronn` `--pipe` <file><br>
-`ronn` &lt; <file>
+`ronn` &lt; <file><br>
+`ronn` `-E`|`--encoding` <encoding> ...
 
 ## DESCRIPTION
 
@@ -35,6 +36,9 @@ The `ronn` command expects input to be valid ronn-format(7) text.  Source files
 are typically named <name>.<section>.ronn (e.g., `example.1.ronn`).  The <name>
 and <section> should match the name and section defined in the <file>'s heading.
 
+Source files must be in UTF-8 encoding, or the encoding specified by the
+`-E`/`--encoding` option, regardless of the locale that `ronn` is running under.
+
 When building roff or HTML output files, destination filenames are determined by
 taking the basename of the input <file> and adding the appropriate file
 extension (or removing the file extension in the case of roff output).  For
@@ -78,6 +82,11 @@ directly to a man pager.
   * `-o`=<directory>, `--output-dir`=<directory>:
     Write generated files to the specified directory instead of the default
     location.
+  
+  * `-E`=<encoding>, `--encoding`=<encoding:
+    Specify the encoding that input files are in. Default is UTF-8, regardless
+    of user's locale settings. Input sent to STDIN is always treated as UTF-8,
+    regardless of whether `-E` is passed.
 
 Format options control the files `ronn` generates, or the output format when the
 `--pipe` argument is specified. When no format options are given, both `--roff`

data/ronn-ng.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
   s.name = 'ronn-ng'
-  s.version = '0.9.0'
-  s.date = '2019-12-21'
+  s.version = '0.9.1'
+  s.date = '2020-04-09'
 
   s.summary     = 'Builds man pages from Markdown'
   s.description = 'Ronn-NG builds manuals in HTML and Unix man page format from Markdown.'
@@ -103,7 +103,6 @@ Gem::Specification.new do |s|
     test/titleless_document.ronn
     test/underline_spacing_test.roff
     test/underline_spacing_test.ronn
-    test/url_formatting.ronn
   ]
   # = MANIFEST =
 

data/test/markdown_syntax.roff

@@ -37,7 +37,7 @@ Inline markup like _italics_,  **bold**, and `code()`\.
 .SS "Philosophy"
 Markdown is intended to be as easy\-to\-read and easy\-to\-write as is feasible\.
 .P
-Readability, however, is emphasized above all else\. A Markdown\-formatted document should be publishable as\-is, as plain text, without looking like it\'s been marked up with tags or formatting instructions\. While Markdown\'s syntax has been influenced by several existing text\-to\-HTML filters \-\- including Setext \fI\%http://docutils\.sourceforge\.net/mirror/setext\.html\fR, atx \fI\%http://www\.aaronsw\.com/2002/atx/\fR, Textile \fI\%http://textism\.com/tools/textile/\fR, reStructuredText \fI\%http://docutils\.sourceforge\.net/rst\.html\fR, Grutatext \fI\%http://www\.triptico\.com/software/grutatxt\.html\fR, and EtText \fI\%http://ettext\.taint\.org/doc/\fR \-\- the single biggest source of inspiration for Markdown\'s syntax is the format of plain text email\.
+Readability, however, is emphasized above all else\. A Markdown\-formatted document should be publishable as\-is, as plain text, without looking like it\'s been marked up with tags or formatting instructions\. While Markdown\'s syntax has been influenced by several existing text\-to\-HTML filters \-\- including Setext \fIhttp://docutils\.sourceforge\.net/mirror/setext\.html\fR, atx \fIhttp://www\.aaronsw\.com/2002/atx/\fR, Textile \fIhttp://textism\.com/tools/textile/\fR, reStructuredText \fIhttp://docutils\.sourceforge\.net/rst\.html\fR, Grutatext \fIhttp://www\.triptico\.com/software/grutatxt\.html\fR, and EtText \fIhttp://ettext\.taint\.org/doc/\fR \-\- the single biggest source of inspiration for Markdown\'s syntax is the format of plain text email\.
 .P
 To this end, Markdown\'s syntax is comprised entirely of punctuation characters, which punctuation characters have been carefully chosen so as to look like what they mean\. E\.g\., asterisks around a word actually look like *emphasis*\. Markdown lists look like, well, lists\. Even blockquotes look like quoted passages of text, assuming you\'ve ever used email\.
 .SS "Inline HTML"
@@ -111,7 +111,7 @@ AT&T
 .fi
 .IP "" 0
 .P
-Similarly, because Markdown supports \fI\%#html\fR, if you use angle brackets as delimiters for HTML tags, Markdown will treat them as such\. But if you write:
+Similarly, because Markdown supports \fIinline HTML\fR, if you use angle brackets as delimiters for HTML tags, Markdown will treat them as such\. But if you write:
 .IP "" 4
 .nf
 4 < 5
@@ -134,9 +134,9 @@ The implication of the "one or more consecutive lines of text" rule is that Mark
 .P
 When you \fIdo\fR want to insert a \fB<br />\fR break tag using Markdown, you end a line with two or more spaces, then type return\.
 .P
-Yes, this takes a tad more effort to create a \fB<br />\fR, but a simplistic "every line break is a \fB<br />\fR" rule wouldn\'t work for Markdown\. Markdown\'s email\-style \fI\%#blockquote\fR and multi\-paragraph \fI\%#list\fR work best \-\- and look better \-\- when you format them with hard breaks\.
+Yes, this takes a tad more effort to create a \fB<br />\fR, but a simplistic "every line break is a \fB<br />\fR" rule wouldn\'t work for Markdown\. Markdown\'s email\-style \fIblockquoting\fR and multi\-paragraph \fIlist items\fR work best \-\- and look better \-\- when you format them with hard breaks\.
 .SS "Headers"
-Markdown supports two styles of headers, Setext \fI\%http://docutils\.sourceforge\.net/mirror/setext\.html\fR and atx \fI\%http://www\.aaronsw\.com/2002/atx/\fR\.
+Markdown supports two styles of headers, Setext \fIhttp://docutils\.sourceforge\.net/mirror/setext\.html\fR and atx \fIhttp://www\.aaronsw\.com/2002/atx/\fR\.
 .P
 Setext\-style headers are "underlined" using equal signs (for first\-level headers) and dashes (for second\-level headers)\. For example:
 .IP "" 4
@@ -900,8 +900,8 @@ _   underscore
 .SH "AUTHOR"
 Markdown was created by John Gruber\.
 .P
-Manual page by Ryan Tomayko\. It\'s pretty much a direct copy of the Markdown Syntax Reference \fI\%http://daringfireball\.net/projects/markdown/syntax\fR, also by John Gruber\.
+Manual page by Ryan Tomayko\. It\'s pretty much a direct copy of the Markdown Syntax Reference \fIhttp://daringfireball\.net/projects/markdown/syntax\fR, also by John Gruber\.
 .SH "SEE ALSO"
 ronn(5)
 .br
-\fI\%http://daringfireball\.net/projects/markdown/\fR
+\fIhttp://daringfireball\.net/projects/markdown/\fR

data/test/section_reference_links.roff

@@ -4,4 +4,4 @@
 .SH "SECTION 1"
 See the following section\.
 .SH "SECTION 2"
-See \fI\%#SECTION\-1\fR or \fI\%#SECTION\-1\fR or even \fI\%#SECTION\-1\fR
+See \fISECTION 1\fR or \fIto put it another way\fR or even \fIlike this\fR

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ronn-ng
 version: !ruby/object:Gem::Version
-  version: 0.9.0
+  version: 0.9.1
 platform: ruby
 authors:
 - Andrew Janke
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2019-12-21 00:00:00.000000000 Z
+date: 2020-04-09 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: kramdown
@@ -28,42 +28,42 @@ dependencies:
   name: mustache
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.7.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.7'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.7.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.7.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.7'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.7.0
 - !ruby/object:Gem::Dependency
   name: nokogiri
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.9.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.9'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.9.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 1.9.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '1.9'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 1.9.0
 - !ruby/object:Gem::Dependency
   name: rack
   requirement: !ruby/object:Gem::Requirement
@@ -88,62 +88,62 @@ dependencies:
   name: rake
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 12.3.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '12.3'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 12.3.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 12.3.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '12.3'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 12.3.0
 - !ruby/object:Gem::Dependency
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.57.1
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.60'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.57.1
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 0.57.1
     - - "~>"
       - !ruby/object:Gem::Version
         version: '0.60'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 0.57.1
 - !ruby/object:Gem::Dependency
   name: sinatra
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 2.0.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '2.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.0.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
-      - !ruby/object:Gem::Version
-        version: 2.0.0
     - - "~>"
       - !ruby/object:Gem::Version
         version: '2.0'
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: 2.0.0
 - !ruby/object:Gem::Dependency
   name: test-unit
   requirement: !ruby/object:Gem::Requirement
@@ -257,7 +257,6 @@ files:
 - test/titleless_document.ronn
 - test/underline_spacing_test.roff
 - test/underline_spacing_test.ronn
-- test/url_formatting.ronn
 homepage: https://github.com/apjanke/ronn-ng
 licenses:
 - MIT
@@ -284,7 +283,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.6
+rubygems_version: 3.1.2
 signing_key: 
 specification_version: 4
 summary: Builds man pages from Markdown

data/test/url_formatting.ronn

@@ -1,3 +0,0 @@
-# URL formatting
-
-Documentation of the Emily programming language can be found at <http://emilylang.org> or <http://bitbucket.org/runhello/emily>.