version 0.9.0

CHANGES

@@ -1,6 +1,12 @@
 Ronn-NG CHANGES
 ===============
 
+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)
 --------------------------
 

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    ronn-ng (0.8.2)
+    ronn-ng (0.9.0)
       kramdown (~> 2.1)
       mustache (~> 0.7, >= 0.7.0)
       nokogiri (~> 1.9, >= 1.9.0)
@@ -15,7 +15,7 @@ GEM
     mini_portile2 (2.4.0)
     mustache (0.99.8)
     mustermann (1.0.3)
-    nokogiri (1.10.5)
+    nokogiri (1.10.7)
       mini_portile2 (~> 2.4.0)
     parallel (1.17.0)
     parser (2.6.3.0)

doc-src/Developer-Guide.md

@@ -4,7 +4,7 @@ Ronn-NG Developer's Guide
 ## Release checklist
 
 * Update the version in files
-  * ronn-ng.gemspec
+  * ronn-ng.gemspec (update the release date, too)
   * `lib/ronn.rb`
 * Update `CHANGES` with the release date
 * Regenerate the man pages with `rake man`

lib/ronn.rb

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

man/ronn-format.7

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.8.2
-.\" http://github.com/apjanke/ronn-ng/tree/0.8.2
-.TH "RONN\-FORMAT" "7" "December 2018" "Ronn-NG 0.8.2" "Ronn Manual"
+.\" 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"
 .SH "NAME"
 \fBronn\-format\fR \- manual authoring format based on Markdown
 .SH "SYNOPSIS"
@@ -85,7 +85,7 @@ Section headings should be all uppercase and may not contain inline markup\.
 .SH "INLINE MARKUP"
 Manpages have a limited set of text formatting capabilities\. There\'s basically \fBboldface\fR and \fIitalics\fR (often displayed using \fIunderline\fR)\. Ronn uses the following bits of markdown(7) to accomplish this:
 .TP
-\fB`backticks`\fR (markdown compatible)
+\fB\e`backticks\e`\fR (markdown compatible)
 Code, flags, commands, and noun\-like things; typically displayed in in \fBboldface\fR\. All text included within \fBbackticks\fR is displayed literally; other inline markup is not processed\. HTML output: \fB<code>\fR\.
 .TP
 \fB**double\-stars**\fR (markdown compatible)

man/ronn.1

@@ -1,6 +1,6 @@
-.\" generated with Ronn-NG/v0.8.2
-.\" http://github.com/apjanke/ronn-ng/tree/0.8.2
-.TH "RONN" "1" "August 2019" "Ronn-NG 0.8.2" "Ronn Manual"
+.\" 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"
 .SH "NAME"
 \fBronn\fR \- convert markdown files to manpages
 .SH "SYNOPSIS"

ronn-ng.gemspec

@@ -1,7 +1,7 @@
 Gem::Specification.new do |s|
   s.name = 'ronn-ng'
-  s.version = '0.8.2'
-  s.date = '2019-03-05'
+  s.version = '0.9.0'
+  s.date = '2019-12-21'
 
   s.summary     = 'Builds man pages from Markdown'
   s.description = 'Ronn-NG builds manuals in HTML and Unix man page format from Markdown.'