nronn 0.10.1.pre2

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 410aa4724fdfc614d9ff8362875481eb7655d37f9d85f0d5bdda18254f3bee08
+  data.tar.gz: 2e90e99b9482707c2a8826d0c03016da1531d453f7d992ca9311f23679c33aa3
+SHA512:
+  metadata.gz: af1d5b921a5a2cce4979660f9542ea64a56a423bb604f91a6503b3423178e90f7b24d2fb4b530c90941bd5ee3413e05d81132f2dd83dccb810d472af85201d44
+  data.tar.gz: f2d9d4aa75de5ceb6a5170ce17f4c1ee82277bf7b782bdb3dbf1f9449370fec0822c4f4468ffd43d05e4fbf77cfc9d41fdb165b3dd1d517dfa2476f582a51a25

data/AUTHORS

@@ -0,0 +1,8 @@
+# This is a list of people who have contributed code or ideas to ronn -- for
+# copyright purposes or whatever.
+
+Ryan Tomayko         <https://github.com/rtomayko>
+Chris Wanstrath      <https://github.com/defunkt>
+Suraj N. Kurapati    <https://github.com/sunaku>
+Hallison Batista     <https://github.com/hallison>
+Andrew Janke         <https://github.com/apjanke>

data/CHANGES

@@ -0,0 +1,230 @@
+Ronn-NG CHANGES
+===============
+
+Version 0.10.1 (in progress)
+----------------------------
+
+* Switch to GitHub Flavored Markdown, fixing code block rendering (<https://github.com/apjanke/ronn-ng/pull/53>)
+* Revert `\[ci]` back to `\(bu)` (<https://github.com/apjanke/ronn-ng/pull/51>)
+* Minor fix to single-quote escaping (<https://github.com/apjanke/ronn-ng/issues/55>)
+* Elide HTML comments when producing roff output (<https://github.com/apjanke/ronn-ng/issues/65>)
+* Bump to mustache 1.x
+* Remove non-portable `more -i` option (<https://github.com/apjanke/ronn-ng/issues/71>)
+
+Version 0.10.0 (never)
+---------------------------
+
+Doesn't exist due to a RubyGems publishing mistake
+
+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)
+---------------------------
+
+* Migrate to kramdown for the underlying Markdown library
+* Minor output formatting and documentation improvements
+
+Version 0.8.2 (2019 Mar 5)
+--------------------------
+
+* Fixes packaging error in 0.8.1
+
+Version 0.8.1 (2019 Mar 5)
+--------------------------
+
+* Fixed URL hyphenation bug. (<https://github.com/apjanke/ronn-ng/issues/23>) (apjanke)
+* Fixed ordered-list bustication. (<https://github.com/apjanke/ronn-ng/issues/24>) (apjanke)
+
+Version 0.8.0 (2018 Dec 25)
+---------------------------
+
+* Added tables support. (apjanke)
+* Lint & Rubocop fixes. (apjanke)
+* Added --output-dir option. (apjanke)
+* Support file names with periods in the name section. (apjanke)
+* Migrated from Hpricot to Nokogiri. (apjanke)
+
+Version 0.7.4 (2018 Dec 22)
+---------------------------
+
+* Forked Ronn-NG from original Ronn. (apjanke)
+* Minor bug fixes: #4, #5 (apjanke)
+
+Original Ronn CHANGES
+=====================
+
+Version 0.7.3 (2010 June 24)
+----------------------------
+
+* Fixed a major bug in roff output due to overly aggressive doublequote
+  escaping. Paragraphs and code blocks were not being displayed if they
+  included a double-quote character. (rtomayko, pawelz)
+
+Version 0.7.0 (2010 June 21)
+----------------------------
+
+* HTML: Manual references (like 'grep(1)', 'ls(1)', etc.) are now hyperlinked
+  based on a set of name -> URL mappings defined in an index.txt file. The index
+  may also define links to things that aren't manuals for use in markdown
+  reference-style links. See the ronn(1) manual on LINK INDEXES for more
+  inforation: <http://rtomayko.github.com/ronn/ronn.1.html#LINK-INDEXES>
+  (rtomayko)
+
+* ROFF: Fixed a bug where multiple dot characters (.) at the beginning of a
+  line were not being escaped properly and were not displayed when viewed
+  in the terminal. (rtomayko)
+
+* ROFF: Non-breaking space characters (&nbsp;) can now be used to control line
+  wrap in roff output. (rtomayko)
+
+* ROFF: Named HTML entities like &bull;, &trade;, &copy;, and &mdash; are now
+  converted to their roff escaped equivalents. (rtomayko)
+
+* An undocumented --markdown format option argument has been added to ronn(1).
+  When given, ronn generates a <name>.<section>.markdown file with the
+  post-processed markdown text. This is mostly useful for debugging but may be
+  useful for converting ronn-format to 100% compatible markdown text.
+  (rtomayko)
+
+* The ronn(5) manpage is now known as ronn-format(7) (section 5 is limited
+  to configuration files and stuff like that historically). The old ronn(7)
+  manpage, which was really just the README, has been removed.
+  (rtomayko)
+
+* Performance improvements. Fixed a few cases where HTML was being reparsed
+  needlessly, tuned dom selectors, ... (rtomayko)
+
+Version 0.6.6 (2010 June 13)
+----------------------------
+
+Small bug fix release fixes whitespace stripping between adjacent
+inline elements in roff output (adamv, rtomayko)
+
+Version 0.6 (2010 June 13)
+--------------------------
+
+Features:
+
+* HTML: New styling system:
+    ronn --style=toc,print program.1.ronn
+    ronn -s dark,toc,/path/to/custom.css man/*.ronn
+
+  The --style (-s) option takes a list of CSS stylesheets to embed into the
+  generated HTML. Stylesheets are inserted in the order specified and can use
+  the cascade to add or remove visual elements.
+
+  Ronn ships with a few built in styles: toc, dark, 80c, and print. You can
+  insert your own by giving the path or manipulating the RONN_STYLE environment
+  variable.
+
+  See ronn(1) for full details on all of these things (rtomayko)
+
+* HTML: It's now possible to generate a Table Of Contents of manpage sections.
+  The TOC is disabled by default. To enable it: ronn --style=toc file.ronn
+  (sunaku)
+
+* HTML: The RONN_LAYOUT environment variable can be used to apply a custom
+  mustache layout template:
+
+  RONN_LAYOUT=mine.mustache ronn man/great-program.1.ronn
+
+  See lib/ronn/template/default.html for default markup and features
+  (defunkt)
+
+* HTML: All heading elements include page anchor id attributes to make
+  it possible to link to a specific manpage section (sunaku)
+
+* HTML: Markdown reference links can be used to refer to sections. To link
+  to the SEE ALSO section of the current manpage, use: [SEE ALSO][], or [to
+  control the link text][SEE ALSO], or even [use the relative URL](#SEE-ALSO).
+  (rtomayko)
+
+* HTML: 80 character terminal style: ronn -s 80c file.ronn -- precisely
+  emulates a 80c terminal (sunaku)
+
+* HTML: Various appearance changes to the default stylesheet: smaller type
+  with consistent vertical baseline; darker type for more contrast; em, var,
+  and u are italic instead of underline (rtomayko)
+
+* HTML: Various print stylesheet tweaks, including hyperlinks and layout
+  enhancements (sunaku)
+
+* ROFF: ronn --warnings (-w) shows troff warnings on stderr when building
+  or viewing manuals. (rtomayko)
+
+* ROFF: Ordered lists. (sunaku)
+
+* ROFF: URLs for hyperlinks are shown immediately after hyperlink text.
+  (sunaku)
+
+* The RONN_MANUAL, RONN_ORGANIZATION, and RONN_DATE environment variables
+  establish the default values of the --manual, --organization, and --date
+  options (rtomayko)
+
+Bugs:
+
+* ROFF: Don't crash with empty preformatted blocks (sunaku)
+
+* ROFF: A whole bunch of weird whitespace related problems in roff output,
+  such as the first line of definition lists being indented by two
+  characters (rtomayko)
+
+* ROFF: All ['".] characters are backslash escaped in roff output. These
+  characters are used for various roff macro syntax (rtomayko)
+
+Deprecations, Obsoletions:
+
+* The ronn(1) command line interface has changed in ways that are not
+  backward-compatible with previous versions of ronn. The --build option is
+  assumed when one or more .ronn files is given on the command line. Previous
+  versions write generated content to standard output with no explicit --build
+  options.
+
+  The default behavior when no files are given remains the same as previous
+  versions: ronn source text is read from stdin and roff is written to stdout.
+
+  See `ronn --help' or the ronn(1) manual for more on command line interface
+  changes.
+
+  (rtomayko, defunkt)
+
+* HTML: Ronn no longer uses a specific monospace font-family; the system
+  default monospace font is used instead. Use 'ronn --style' to set up a font
+  stack (rtomayko)
+
+* HTML: The following HTML elements are deprecated and will be removed at some
+  point: div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .mp, .man-decor, .man-head, .man-foot, .man-title, and .man-navigation
+  classes should be used instead (rtomayko)
+
+* The markdown(5) manpage is no longer shipped with the ronn package. It is
+  shipped with the latest version of rdiscount, however.
+  (rtomayko, sunaku)
+
+0.5 (2010 April 24)
+-------------------
+
+* Fixed a bug in roff output where multiple successive newlines were being
+  collapsed into a single newline in preformatted output.
+
+* Hexadecimal and decimal entity references generated by the Markdown to HTML
+  conversion are now properly decoded into normal characters in roff output.
+
+* The compatibility shims that allowed the ronn command to be invoked as "ron",
+  and the ronn library to be required as "ron", have been removed.
+
+
+0.4 (2010 March 08)
+-------------------
+
+* Ron has been renamed "Ronn", including the "ronn" command and the "ronn"
+  library. Compatibility shims are included in this release but will be removed
+  in the next release.
+
+* The hpricot library is now used for HTML hackery instead of the nokogiri
+  library. The hpricot library is preferred because it doesn't depend on external
+  system dependencies.

data/Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gemspec

data/Gemfile.lock

@@ -0,0 +1,72 @@
+PATH
+  remote: .
+  specs:
+    nronn (0.10.1.pre2)
+      kramdown (~> 2.1)
+      kramdown-parser-gfm (~> 1.0.1)
+      mustache (~> 1.0)
+      nokogiri (~> 1.11, >= 1.11.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.1)
+    kramdown (2.4.0)
+      rexml
+    kramdown-parser-gfm (1.0.1)
+      kramdown (~> 2.0)
+    mini_portile2 (2.8.0)
+    mustache (1.1.1)
+    mustermann (1.1.1)
+      ruby2_keywords (~> 0.0.1)
+    nokogiri (1.13.8)
+      mini_portile2 (~> 2.8.0)
+      racc (~> 1.4)
+    parallel (1.20.1)
+    parser (2.7.2.0)
+      ast (~> 2.4.1)
+    power_assert (1.2.0)
+    racc (1.6.0)
+    rack (2.2.3)
+    rack-protection (2.1.0)
+      rack
+    rainbow (3.0.0)
+    rake (12.3.3)
+    regexp_parser (2.0.1)
+    rexml (3.2.5)
+    rubocop (0.93.1)
+      parallel (~> 1.10)
+      parser (>= 2.7.1.5)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8)
+      rexml
+      rubocop-ast (>= 0.6.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 1.4.0, < 2.0)
+    rubocop-ast (1.3.0)
+      parser (>= 2.7.1.5)
+    ruby-progressbar (1.10.1)
+    ruby2_keywords (0.0.2)
+    sinatra (2.1.0)
+      mustermann (~> 1.0)
+      rack (~> 2.2)
+      rack-protection (= 2.1.0)
+      tilt (~> 2.0)
+    test-unit (3.3.7)
+      power_assert
+    tilt (2.0.10)
+    unicode-display_width (1.7.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  nronn!
+  rack (~> 2.2, >= 2.2.3)
+  rake (~> 12.3, >= 12.3.3)
+  rubocop (~> 0.88, >= 0.88.0)
+  sinatra (~> 2.0, >= 2.0.8)
+  test-unit (~> 3.3, >= 3.3.6)
+
+BUNDLED WITH
+   2.1.4

data/INSTALLING.md

@@ -0,0 +1,92 @@
+nRonn Installation
+====================
+
+## Installation Process
+
+### From a Package Manager
+
+TBD
+### From RubyGems
+
+nRonn is distributed as a gem package, which can be used if you don't have
+a supported package manager. Install with rubygems:
+
+```
+gem install nronn
+ronn --help
+```
+
+nRonn includes completion definitions for bash and zsh, but these are not
+installed into the system locations as part of the gem. You will need to figure 
+out how to install those into your system to make them available in your shell.
+
+A decent way to do this is probably to add symlinks to your system shell
+completion directories pointing at the files in the installed gem.
+
+In Zsh, you can do something like this:
+
+```
+ronn_dist_dir=$(dirname $(dirname $(gem which nronn)))
+ronn_zsh_dir="$ronn_dist_dir/completion/zsh"
+ln -s "$ronn_zsh_dir/_ronn" /usr/local/share/zsh/site-functions
+```
+
+In Bash, something like this:
+
+```
+ronn_dist_dir=$(dirname $(dirname $(gem which nronn)))
+ronn_bash_dir="$ronn_dist_dir/completion/bash"
+ln -s "$ronn_bash_dir/ronn" /usr/local/etc/bash_completion.d
+```
+
+You will need to redo these steps each time you upgrade `nronn` or install
+it into a different Ruby environment. Sorry for the inconvenience; this seems
+to be a limitation of the `gem` installation mechanism.
+
+If that `gem which` stuff doesn't work for you, you can `gem install gem-path`
+and use `gem path nronn` instead.
+
+
+## Building from Source
+
+Hacking? Install nRonn from source.
+
+Clone the git repository and put ronn/bin on your PATH:
+
+```
+git clone git://github.com/apjanke/nronn
+PATH=$(pwd)/nronn/bin:$PATH
+```
+
+The following gems are required for nronn development:
+ * nokogiri
+ * mustache
+ * kramdown
+ * rubocop
+ * sinatra
+ * rack
+ * rake
+ * test-unit
+
+```
+gem install nokogiri mustache kramdown rubocop sinatra rack rake test-unit
+```
+
+Or install them with bundler using the project's gem definition:
+
+```
+bundle install --with development
+```
+
+Then you should be able to make changes directly to your cloned repo and have
+them be reflected in your active `ronn` command.
+
+## Legacy Versions
+
+Historical Ronn tarballs available at [the original Ronn repo](https://github.com/n-ronn/nronn/tags).
+
+```
+curl -L https://github.com/n-ronn/nronn/archive/refs/tags/0.6.6.tar.gz | tar xvzf -
+cd rtomayko-r*
+ruby setup.rb
+```

data/LICENSE.txt

@@ -0,0 +1,12 @@
+The MIT License
+
+       Copyright (C) 2009 Ryan Tomayko <tomayko.com/about>
+       Copyright (C) 2018, 2019 Andrew Janke <apjanke.net>
+       Copyright (C) 2022 Takuya Noguchi <takninnovationresearch@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+       

data/README.md

@@ -0,0 +1,131 @@
+# nRonn
+
+nRonn is a new, currently-maintained fork of the defunct [original Ronn
+project](https://github.com/rtomayko/ronn).
+
+Ronn builds manuals. It converts simple, human readable textfiles to roff for
+terminal display, and also to HTML for the web.
+
+The source format includes all of Markdown but has a more rigid structure and
+syntax extensions for features commonly found in manpages (definition lists,
+link notation, etc.). The ronn-format(7) manual page defines the format in
+detail.
+
+The `*.ronn` files found in the [`man/`][1] directory show off a wide range of
+ronn capabilities:
+
+* [ronn(1)](http://rtomayko.github.com/ronn/ronn.1) command -
+  [source file](https://github.com/n-ronn/nronn/blob/master/man/ronn.1.ronn),
+  [roff output](https://github.com/n-ronn/nronn/blob/master/man/ronn.1)
+
+* [ronn-format(7)](http://rtomayko.github.com/ronn/ronn-format.7) -
+  [source file](https://github.com/n-ronn/nronn/blob/master/man/ronn-format.7.ronn),
+  [roff output](https://github.com/n-ronn/nronn/blob/master/man/ronn-format.7)
+
+[1]: https://github.com/n-ronn/nronn/tree/master/man
+
+As an alternative, you might want to check out [pandoc](http://johnmacfarlane.net/pandoc/) which can also convert markdown into roff manual pages.
+
+## Installation
+
+Install with `gem` anywhere that supports it:
+
+```bash
+gem install nronn
+```
+
+See [INSTALLING.md](INSTALLING.md) for details on other systems and installation methods.
+
+## Examples
+
+Build roff and HTML output files for one or more input files:
+
+```bash
+$ ronn man/ronn.5.ronn
+roff: man/ronn.5
+html: man/ronn.5.html
+```
+
+Generate only a standalone HTML version of one or more files:
+
+```bash
+$ ronn --html man/markdown.5.ronn
+html: man/markdown.5.html
+```
+
+Build roff versions of all ronn files in a directory:
+
+```bash
+$ ronn --roff man/*.ronn
+```
+
+View a ronn file as if it were a manpage without building intermediate files:
+
+```bash
+$ ronn --man man/markdown.5.ronn
+```
+
+View roff output with man(1):
+
+```bash
+$ man man/ronn.5
+```
+
+The [ronn(1)](http://rtomayko.github.com/ronn/ronn.1) manual page includes
+comprehensive documentation on `ronn` command line options.
+
+## Background
+
+Some think Unix manual pages are a poor and outdated form of documentation. nRonn
+disagrees:
+
+* Manpages follow a well defined structure that's immediately familiar. This
+  gives developers a starting point when documenting new tools, libraries, and
+  formats.
+
+* Manpages get to the point. Because they're written in an inverted style, with
+  a SYNOPSIS section followed by additional detail, prose and references to
+  other sources of information, manpages provide the best of both cheat sheet
+  and reference style documentation.
+
+* Historically, manpages use an extremely — unbelievably — limited set of
+  text formatting capabilities. You get a couple of headings, lists, bold,
+  underline and no more. This is a feature.
+
+* Although two levels of section hierarchy are technically supported, most
+  manpages use only a single level. Unwieldy document hierarchies complicate
+  otherwise good documentation. Remember that Feynman covered all of physics
+  — heavenly bodies through QED — with only two levels of document hierarchy
+  (_The Feynman Lectures on Physics_, 1970).
+
+* The classical terminal manpage display is typographically well thought out.
+  Big bold section headings, justified monospace text, nicely indented
+  paragraphs, intelligently aligned definition lists, and an informational
+  header and footer.
+
+* Manpages have a simple referencing syntax; e.g., sh(1), fork(2), markdown(7).
+  HTML versions can use this to generate links between pages.
+
+Unfortunately, figuring out how to create a manpage is a fairly tedious process.
+The roff/mandoc/mdoc macro languages are highly extensible, fractured between
+multiple dialects, and include a bunch of device-specific stuff irrelevant to
+modern publishing tools. Ronn aims to solve that problem.
+
+## Requirements
+
+Ruby 2.3 or newer, and gems as listed in `nronn.gemspec`.
+
+## Project Management
+
+The project home page is at <https://github.com/n-ronn/nronn>. Bug reports,
+feature requests, and patch submissions are welcome.
+
+## License and Copying
+
+MIT License.
+
+See [LICENSE.txt](LICENSE.txt) for detail.
+
+## Build Status
+
+TODO