[Debian-astro-commits] [cspice] 03/11: d/man: Switch to markdown and rewrite
Rock Storm
rockstorm-guest at moszumanska.debian.org
Sun Apr 23 17:34:47 UTC 2017
This is an automated email from the git hooks/post-receive script.
rockstorm-guest pushed a commit to branch debian
in repository cspice.
commit 16bbabd245e2627daee759f9a0b58dcef783164d
Author: Rock Storm <rockstorm at gmx.com>
Date: Sun Apr 23 10:55:09 2017 +0200
d/man: Switch to markdown and rewrite
---
debian/man/cspice-brief.1 | 229 +++++++++++++++++---------------
debian/man/cspice-brief.md | 158 ++++++++++++++++++++++
debian/man/cspice-chronos.1 | 229 +++++++++++++++++---------------
debian/man/cspice-chronos.md | 132 +++++++++++++++++++
debian/man/cspice-ckbrief.1 | 150 +++++++++++----------
debian/man/cspice-ckbrief.md | 123 +++++++++++++++++
debian/man/cspice-commnt.1 | 113 +++++++++-------
debian/man/cspice-commnt.md | 60 +++++++++
debian/man/cspice-dskbrief.1 | 90 +++++++++++++
debian/man/cspice-dskbrief.md | 89 +++++++++++++
debian/man/cspice-dskexp.1 | 213 ++++++++++++++++++++++++++++++
debian/man/cspice-dskexp.md | 145 ++++++++++++++++++++
debian/man/cspice-frmdiff.1 | 299 +++++++++++++++++++++++-------------------
debian/man/cspice-frmdiff.md | 196 +++++++++++++++++++++++++++
debian/man/cspice-inspekt.1 | 44 +++----
debian/man/cspice-inspekt.md | 27 ++++
debian/man/cspice-mkdsk.1 | 79 +++++++++++
debian/man/cspice-mkdsk.md | 73 +++++++++++
debian/man/cspice-mkspk.1 | 107 ++++++++-------
debian/man/cspice-mkspk.md | 91 +++++++++++++
debian/man/cspice-msopck.1 | 81 +++++++-----
debian/man/cspice-msopck.md | 62 +++++++++
debian/man/cspice-spacit.1 | 52 ++++----
debian/man/cspice-spacit.md | 36 +++++
debian/man/cspice-spkdiff.1 | 203 ++++++++++++++++------------
debian/man/cspice-spkdiff.md | 163 +++++++++++++++++++++++
debian/man/cspice-spkmerge.1 | 54 ++++----
debian/man/cspice-spkmerge.md | 34 +++++
debian/man/cspice-tobin.1 | 53 ++++----
debian/man/cspice-tobin.md | 46 +++++++
debian/man/cspice-toxfr.1 | 53 ++++----
debian/man/cspice-toxfr.md | 45 +++++++
debian/man/cspice-version.1 | 59 +++++----
debian/man/cspice-version.md | 41 ++++++
debian/man/cspice.7 | 194 ++++++++++++++++-----------
debian/man/cspice.md | 142 ++++++++++++++++++++
36 files changed, 3101 insertions(+), 864 deletions(-)
diff --git a/debian/man/cspice-brief.1 b/debian/man/cspice-brief.1
index e8f6351..2a0cec2 100644
--- a/debian/man/cspice-brief.1
+++ b/debian/man/cspice-brief.1
@@ -1,111 +1,126 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-BRIEF 1
-.SH NAME
-cspice-brief \- displays a summary for binary SPK or binary PCK files
-.SH SYNOPSIS
-.B cspice-brief
-.RI [OPTIONS]
-.RI FILE
-[\fIFILE\fR ...]
-.SH DESCRIPTION
-.B cspice-brief
-displays a contents and time coverage summary for one or more binary SPK or binary PCK files.
-It can display a summary for each individual file listed on the command line, in a list file, and/or a meta-kernel, or for all files as if they were combined into a single file. It can display coverage boundaries as Ephemeris Times (ET) in calendar format, if requested rounded to the nearest second, minute, hour, or day, as ET seconds past J2000, as UTC times in "year-month-day" format , or as UTC times in "day-of-year" format. The program can restrict summary display to only specified b [...]
-.PP
-An LSK file must be provided on the command line to display times in UTC formats. FK file(s) must be provided on the command line to display names of any frames that are not built into the Toolkit.
-.PP
-.B cspice-brief
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
-.SS Options Controlling Output Summary Format
-.TP
-.BR \-c
-Display bodies/frames in the format that shows their centers-of-motion (for SPKs) or relative-to-frames (for binary PCKs).
-.TP
-.BR \-a
-Treat all files as a single file. Display combined summary for all files as if all data from these files were merged into a single file.
-.TP
-.BR \-t
-Display summary in a tabular format.
-.TP
-.BR \-s
-Re-order records in the tables of the tabular output in such way that the records for a particular body or frame are grouped together and sorted by the start time within each group. This option supersedes \fB\-g\fR and has no effect without \fB\-t\fR. This option re-sorts tabular display tables already ordered by \fB\-o\fR.
-.TP
-.BR \-g
-Re-order records in the tables of the tabular output such that all records with the same coverage are grouped together. This option has no effect without \fB\-t\fR and it regroups tables already ordered by \fB\-o\fR.
-.TP
-.BR \-n
-Display bodies/frames using numeric IDs ("ID") rather than the default name/ID combinations ("NAME (ID)").
-.TP
-.BR \-o
-Order bodies/frames in the table headers in the default display, or in the left columns in the tabular display, by name rather than by numeric ID. This option is ignored when \fB\-n\fR is specified.
-\br
-.SS Options Controlling Output Time Format
-.TP
-.BR \-etsec
-Display time tags as ET seconds past J2000 in the "SSSSSSSSSSSS.DDDDDD" format.
-.TP
-.BR \-utc
-Display time tags as UTC in the "YYYY-MON-DD HR:MN:SC.DDD" format (needs LSK).
-.TP
-.BR \-utcdoy
-Display time tags as UTC times in the "YYYY-DOY // HR:MN:SC.DDD" format (needs LSK).
-.TP
-.BR \-sec
-Display default calendar ET time tags "rounded inward" to the nearest second.
-This option has no effect when either \fB\-etsec\fR, \fB\-utc\fR or \fB\-utcdoy\fR is used.
-If more than one of the \fB\-sec\fR, \fB\-min\fR, \fB\-hour\fR, and \fB\-day\fR options is specified, the one providing the "highest" time resolution takes precedence, namely \fB\-sec\fR > \fB\-min\fR > \fB\-hour\fR > \fB\-day\fR.
-.TP
-.BR \-min
-Display default calendar ET time tags "rounded inward" to the nearest minute.
-Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well.
-.TP
-.BR \-hour
-Display default calendar ET time tags "rounded inward" to the nearest hour.
-Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well.
-.TP
-.BR \-day
-Display default calendar ET time tags "rounded inward" to the nearest day.
-Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well.
-.SS Options Filtering Summary
-.TP
-\fB\-sb\fR\fIBODY\fR, \fB\-sb\fR\fI[MIN,MAX]\fR, \fB\-\fR\fIBODY\fR
-Display summary information only for the specified body/frame name or numeric ID \fIBODY\fR. The use of just \fB\-\fR followed by the body/frame name or numeric ID is deprecated.
-If the body/frame name contains spaces, these spaces must be replaced with underscores ("_").
-A range of numeric IDs in the form \fI[MIN,MAX]\fR may be used instead of a single name or numeric ID. The range can be open on either end, producing a summary for all numeric IDs greater than the specified value (\fI[MIN,:]\fR) or less than the specified value (\fI[:,MAX]\fR).
-Up to 100 individual \fB\-sb\fR and \fB\-sc\fR constraints can be specified at the same time, they will be combined using logical "OR".
-.TP
-\fB\-sc\fR\fICENTER\fR, \fB\-sc\fR\fI[MIN,MAX]\fR
-Display summary information only for the specified center-of-motion/relative-to-frame name or numeric ID \fICENTER\fR.
-Formatting rules for the \fB\-sb\fR option apply to this option as well.
-.TP
-\fB\-at\fR \fITIME\fR
-Display summary information only for the bodies/frames whose coverage intervals contains the specified \fITIME\fR.
-The time can be provided in any format supported by SPICE's TPARSE routine as long as it doesn't contain spaces.
-This option overrides \fB\-from\fR/\fB\-to\fR.
-.TP
-\fB\-from\fR \fITIME\fR \fB\-to\fR \fITIME\fR
-Display summary information only for the bodies/frames whose coverages contain the specified time interval.
-Formatting rules for the \fB\-at\fR option apply to this option as well.
-If either \fB\-from\fR or \fB\-to\fR is specified by itself it has the same effect as the \fB\-at\fR option.
-If the time provided with \fB\-from\fR is later than the time provided with \fB\-to\fR they will be re-ordered internally.
-.SS Miscellaneous Options
-.TP
-\fB\-f\fR \fILIST_FILE\fR
-Display a summary for the files whose names are listed in the text file \fILIST_FILE\fR.
-The file names can be provided one-per-line or a few-per-line separated by one or more spaces.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-BRIEF" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-brief\fR \- displays a summary for binary SPK or binary PCK files
+.
+.SH "SYNOPSIS"
+\fBcspice brief\fR [\fIoptions\fR] \fIfile\fR [\fIfile\fR \.\.\.]
+.
+.SH "DESCRIPTION"
+\fBBRIEF\fR is a command line program that displays summary of the contents and time coverage for one or more binary SPK or binary PCK files\.
+.
+.P
+The program can display a summary for each individual file listed on the command line, in a list file, and/or a meta\-kernel, or for all files as if they were combined into a single file\. It can display coverage boundaries as Ephemeris Times (ET) in calendar format, if requested rounded to the nearest second, minute, hour, or day, as ET seconds past J2000, as UTC times in "year\-month\-day" format , or as UTC times in "day\-of\-year" format\.
+.
+.P
+\fBBRIEF\fR can restrict summary display to only specified bodies or frames and/or specified centers\-of\-motion or relative\-to\-frames and/or for a specified time or time interval\. It can display the summary in a variety of formats, ordered by body or frame names or numeric IDs, with or without showing centers\-of\-motion or relative\-to\-frames\.
+.
+.P
+An LSK file must be provided on the command line to display times in UTC formats\. FK file(s) must be provided on the command line to display names of any frames that are not built into the Toolkit\.
+.
+.P
+\fBBRIEF\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+.
+.SS "Options Controlling Output Summary Format"
+.
+.TP
+\fB\-c\fR
+Display bodies/frames in the format that shows their centers\-of\-motion (for SPKs) or relative\-to\-frames (for binary PCKs)\.
+.
+.TP
+\fB\-a\fR
+Treat all files as a single file\. Display combined summary for all files as if all data from these files were merged into a single file\.
+.
+.TP
+\fB\-t\fR
+Display summary in a tabular format\.
+.
+.TP
+\fB\-s\fR
+Re\-order records in the tables of the tabular output in such way that the records for a particular body or frame are grouped together and sorted by the start time within each group\. This option supersedes \fB\-g\fR and has no effect without \fB\-t\fR\. This option re\-sorts tabular display tables already ordered by \fB\-o\fR\.
+.
+.TP
+\fB\-g\fR
+Re\-order records in the tables of the tabular output such that all records with the same coverage are grouped together\. This option has no effect without \fB\-t\fR and it regroups tables already ordered by \fB\-o\fR\.
+.
+.TP
+\fB\-n\fR
+Display bodies/frames using numeric IDs ("ID") rather than the default name/ID combinations ("NAME (ID)")\.
+.
+.TP
+\fB\-o\fR
+Order bodies/frames in the table headers in the default display, or in the left columns in the tabular display, by name rather than by numeric ID\. This option is ignored when \fB\-n\fR is specified\.
+.
+.SS "Options Controlling Output Time Format"
+If more than one of the \fB\-sec\fR, \fB\-min\fR, \fB\-hour\fR, and \fB\-day\fR options is specified, the one providing the "highest" time resolution takes precedence, namely \fB\-sec\fR > \fB\-min\fR > \fB\-hour\fR > \fB\-day\fR\.
+.
+.TP
+\fB\-etsec\fR
+Display time tags as ET seconds past J2000 in the "SSSSSSSSSSSS\.DDDDDD" format\.
+.
+.TP
+\fB\-utc\fR
+Display time tags as UTC in the "YYYY\-MON\-DD HR:MN:SC\.DDD" format (needs LSK)\.
+.
+.TP
+\fB\-utcdoy\fR
+Display time tags as UTC times in the "YYYY\-DOY // HR:MN:SC\.DDD" format (needs LSK)\.
+.
+.TP
+\fB\-sec\fR
+Display default calendar ET time tags "rounded inward" to the nearest second\. This option has no effect when either \fB\-etsec\fR, \fB\-utc\fR or \fB\-utcdoy\fR is used\.
+.
+.TP
+\fB\-min\fR
+Display default calendar ET time tags "rounded inward" to the nearest minute\. Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well\.
+.
+.TP
+\fB\-hour\fR
+Display default calendar ET time tags "rounded inward" to the nearest hour\. Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well\.
+.
+.TP
+\fB\-day\fR
+Display default calendar ET time tags "rounded inward" to the nearest day\. Effectiveness and precedence rules for the \fB\-sec\fR apply to this option as well\.
+.
+.SS "Options Filtering Summary"
+.
+.TP
+\fB\-sb\fR\fIbod\fR, \fB\-sb\fR\fI[min,max]\fR, \fB\-\fR\fIbod\fR
+Display summary information only for the specified body/frame name or numeric ID \fIbod\fR\. The use of just \fB\-\fR followed by the body/frame name or numeric ID is deprecated\. If the body/frame name contains spaces, these spaces must be replaced with underscores ("_")\. A range of numeric IDs in the form \fI[min,max]\fR may be used instead of a single name or numeric ID\. The range can be open on either end, producing a summary for all numeric IDs greater than the specified value (\f [...]
+.
+.TP
+\fB\-sc\fR\fIcen\fR, \fB\-sc\fR\fI[min,max]\fR
+Display summary information only for the specified center\-of\-motion/relative\-to\-frame name or numeric ID \fIcen\fR\. Formatting rules for the \fB\-sb\fR option apply to this option as well\.
+.
+.TP
+\fB\-at\fR \fItime\fR
+Display summary information only for the bodies/frames whose coverage intervals contains the specified \fItime\fR\. The time can be provided in any format supported by SPICE\'s TPARSE routine as long as it doesn\'t contain spaces\. This option overrides \fB\-from\fR/\fB\-to\fR\.
+.
+.TP
+\fB\-from\fR \fIbeg\fR \fB\-to\fR \fIend\fR
+Display summary information only for the bodies/frames whose coverages contain the specified time interval\. Formatting rules for the \fB\-at\fR option apply to this option as well\. If either \fB\-from\fR or \fB\-to\fR is specified by itself it has the same effect as the \fB\-at\fR option\. If the time provided with \fB\-from\fR is later than the time provided with \fB\-to\fR they will be re\-ordered internally\.
+.
+.SS "Miscellaneous Options"
+.
+.TP
+\fB\-f\fR \fIlist\fR
+Display a summary for the files whose names are listed in the text file \fIlist\fR\. The file names can be provided one\-per\-line or a few\-per\-line separated by one or more spaces\.
+.
.TP
\fB\-h\fR
-Display a complete usage message listing all options and exit.
+Display a complete usage message listing all options and exit\.
+.
.TP
\fB\-v\fR
-Display just the version line and exit.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+Display just the version line and exit\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on http://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-brief.md b/debian/man/cspice-brief.md
new file mode 100644
index 0000000..3e2fb15
--- /dev/null
+++ b/debian/man/cspice-brief.md
@@ -0,0 +1,158 @@
+cspice-brief(1) -- displays a summary for binary SPK or binary PCK files
+========================================================================
+
+SYNOPSIS
+--------
+**cspice brief** [_options_] _file_ [_file_ ...]
+
+DESCRIPTION
+-----------
+**BRIEF** is a command line program that displays summary of the contents
+and time coverage for one or more binary SPK or binary PCK files.
+
+The program can display a summary for each individual file listed on the
+command line, in a list file, and/or a meta-kernel, or for all files as if they
+were combined into a single file. It can display coverage boundaries as
+Ephemeris Times (ET) in calendar format, if requested rounded to the nearest
+second, minute, hour, or day, as ET seconds past J2000, as UTC times in
+"year-month-day" format , or as UTC times in "day-of-year" format.
+
+**BRIEF** can restrict summary display to only specified bodies or frames
+and/or specified centers-of-motion or relative-to-frames and/or for a specified
+time or time interval. It can display the summary in a variety of formats,
+ordered by body or frame names or numeric IDs, with or without showing
+centers-of-motion or relative-to-frames.
+
+An LSK file must be provided on the command line to display times in UTC
+formats. FK file(s) must be provided on the command line to display names of
+any frames that are not built into the Toolkit.
+
+**BRIEF** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+### Options Controlling Output Summary Format
+
+ * `-c`:
+ Display bodies/frames in the format that shows their centers-of-motion
+ (for SPKs) or relative-to-frames (for binary PCKs).
+
+ * `-a`:
+ Treat all files as a single file. Display combined summary for all files
+ as if all data from these files were merged into a single file.
+
+ * `-t`:
+ Display summary in a tabular format.
+
+ * `-s`:
+ Re-order records in the tables of the tabular output in such way that
+ the records for a particular body or frame are grouped together and
+ sorted by the start time within each group. This option supersedes
+ **-g** and has no effect without **-t**. This option re-sorts tabular
+ display tables already ordered by **-o**.
+
+ * `-g`:
+ Re-order records in the tables of the tabular output such that all
+ records with the same coverage are grouped together. This option has no
+ effect without **-t** and it regroups tables already ordered by **-o**.
+
+ * `-n`:
+ Display bodies/frames using numeric IDs ("ID") rather than the default
+ name/ID combinations ("NAME (ID)").
+
+ * `-o`:
+ Order bodies/frames in the table headers in the default display, or in
+ the left columns in the tabular display, by name rather than by numeric
+ ID. This option is ignored when **-n** is specified.
+
+### Options Controlling Output Time Format
+
+If more than one of the **-sec**, **-min**, **-hour**, and **-day** options
+is specified, the one providing the "highest" time resolution takes
+precedence, namely **-sec** > **-min** > **-hour** > **-day**.
+
+ * `-etsec`:
+ Display time tags as ET seconds past J2000 in the "SSSSSSSSSSSS.DDDDDD"
+ format.
+
+ * `-utc`:
+ Display time tags as UTC in the "YYYY-MON-DD HR:MN:SC.DDD" format (needs
+ LSK).
+
+ * `-utcdoy`:
+ Display time tags as UTC times in the "YYYY-DOY // HR:MN:SC.DDD" format
+ (needs LSK).
+
+ * `-sec`:
+ Display default calendar ET time tags "rounded inward" to the nearest
+ second. This option has no effect when either **-etsec**, **-utc** or
+ **-utcdoy** is used.
+
+ * `-min`:
+ Display default calendar ET time tags "rounded inward" to the nearest
+ minute. Effectiveness and precedence rules for the **-sec** apply to
+ this option as well.
+
+ * `-hour`:
+ Display default calendar ET time tags "rounded inward" to the nearest
+ hour. Effectiveness and precedence rules for the **-sec** apply to this
+ option as well.
+
+ * `-day`:
+ Display default calendar ET time tags "rounded inward" to the nearest
+ day. Effectiveness and precedence rules for the **-sec** apply to this
+ option as well.
+
+### Options Filtering Summary
+
+ * `-sb`_bod_, `-sb`_[min,max]_, `-`_bod_:
+ Display summary information only for the specified body/frame name or
+ numeric ID _bod_. The use of just **-** followed by the body/frame name or
+ numeric ID is deprecated. If the body/frame name contains spaces, these
+ spaces must be replaced with underscores ("\_"). A range of numeric IDs in
+ the form _[min,max]_ may be used instead of a single name or numeric ID.
+ The range can be open on either end, producing a summary for all numeric
+ IDs greater than the specified value (_[min,:]_) or less than the specified
+ value (_[:,max]_). Up to 100 individual **-sb** and **-sc** constraints can
+ be specified at the same time, they will be combined using logical "OR".
+
+ * `-sc`_cen_, `-sc`_[min,max]_:
+ Display summary information only for the specified
+ center-of-motion/relative-to-frame name or numeric ID _cen_. Formatting
+ rules for the **-sb** option apply to this option as well.
+
+ * `-at` _time_:
+ Display summary information only for the bodies/frames whose coverage
+ intervals contains the specified _time_. The time can be provided in any
+ format supported by SPICE's TPARSE routine as long as it doesn't contain
+ spaces. This option overrides **-from**/**-to**.
+
+ * `-from` _beg_ `-to` _end_:
+ Display summary information only for the bodies/frames whose coverages
+ contain the specified time interval. Formatting rules for the **-at**
+ option apply to this option as well. If either **-from** or **-to** is
+ specified by itself it has the same effect as the **-at** option. If the
+ time provided with **-from** is later than the time provided with **-to**
+ they will be re-ordered internally.
+
+### Miscellaneous Options
+
+ * `-f` _list_:
+ Display a summary for the files whose names are listed in the text file
+ _list_. The file names can be provided one-per-line or a few-per-line
+ separated by one or more spaces.
+
+ * `-h`:
+ Display a complete usage message listing all options and exit.
+
+ * `-v`:
+ Display just the version line and exit.
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-chronos.1 b/debian/man/cspice-chronos.1
index e53043f..bcb184e 100644
--- a/debian/man/cspice-chronos.1
+++ b/debian/man/cspice-chronos.1
@@ -1,105 +1,124 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-CHRONOS 1
-.SH NAME
-cspice-chronos \- convert time from one supported system/type to another
-.SH SYNOPSIS
-.B cspice-chronos
-\fB\-setup\fR \fIFILE\fR
-.br
-.RS 15
-\fB\-from\fR \fITIME_SYSTEM\fR
-.br
-\fB\-to\fR \fITIME_SYSTEM\fR
-.br
-\fB\-time\fR \fITIME\fR | \fB-batch\fR
-.br
-[\fIOPTIONS\fR]
-
-.SH DESCRIPTION
-\fBcspice-chronos\fR
-is a time conversion tool capable of converting times between the following time systems:
-.br
-.RS 4
-UTC: Universal Time Coordinated (types: SCET, ERT, ETT, LT)
-.br
-ET: Ephemeris Time (types: SCET, ERT, ETT, LT, SECONDS)
-.br
-SCLK: Spacecraft On-board Clock Time (types: SCLK, HEX, TICKS)
-.br
-ST: Local True Solar Time (types: LST, LSU)
-.RE
-.PP
-.B cspice-chronos
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
-.TP
-\fB\-setup\fR \fISETUP_FILE\fR
-Specify a setup file name or directly list the names of the SPICE kernels to be used.
-If \fISETUP_FILE\fR is not present or is blank, it tries to obtain it from the environment variable CHRONOS_SETUP_FILE.
-.TP
-\fB\-from\fR \fITIME_SYSTEM\fR
-Specify the time system of the input time.
-.TP
-\fB\-fromtype\fR \fITIME_TYPE\fR
-Specify the time type of the input time.
-If it's not present or is blank, it is assumed the default time type for the input time system (SCET for UTC and ET, SCLK for SCLK, and LST for LST).
-.TP
-\fB\-to\fR \fITIME_SYSTEM\fR
-Specify the time system of the output time.
-.TP
-\fB\-totype\fR \fITIME_TYPE\fR
-Specify the time type of the output time.
-If it's not present or is blank, it is assumed the default time type for the output time system (SCET for UTC and ET, SCLK for SCLK and LST for LST).
-.TP
-\fB\-format\fR \fIOUTPUT_FORMAT\fR
-Specify a custom format for the output time.
-If a format specification is not present or is blank, it looks for a specification in the setup file and, if such is also not available, it uses the default format.
-.TP
-\fB\-time\fR \fITIME\fR
-Specify the input time.
-Most time types of UTC and ET systems require input time to be in a form of a time string recognized by TIME subsystem of SPICE.
-.TP
-\fB\-batch\fR
-Tell the program to take input time(s) from standard input instead of the command line.
-If it's present, the program ignores any input time provided after the \fB-time\fR option.
-.TP
-\fB\-sc\fR \fISC_ID\fR
-Specify the NAIF ID for the spacecraft.
-If \fISC_ID\fR is not present, the program looks for it in the setup file.
-.TP
-\fB\-center\fR \fIBODY_ID\fR
-Specify the NAIF ID for the center body.
-If \fIBODY_ID\fR is not present, the program looks for it in the setup file.
-.TP
-\fB\-landingtime\fR \fITIME\fR
-Specify the UTC time of the landing.
-If \fITIME\Fr is not present, the program looks for it in the setup file.
-.TP
-\fB\-sol1index\fR \fIINDEX\fR
-Specify the SOL index for the first day on surface.
-If \fIINDEX\fR is not present, the program looks for it in the setup file.
-.TP
-\fB\-nolabel\fR
-Tell the program to not display [SYSTEM]/[TYPE] following the output time string.
-.TP
-\fB\-trace\fR
-Tell the program to display trace information including, complete command line, names of the loaded SPICE kernel files, all relevant setup information, etc.
-This option overrules the \fB-nolabel\fR option.
-.TP
-\fB\-template\fR
-Display setup file template.
-.TP
-\fB\-h\fR, \fB\-help\fR
-Display help information.
-.TP
-\fB\-u\fR, \fB\-usage\fR
-Display usage information.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-CHRONOS" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-chronos\fR \- convert time from one supported system/type to another
+.
+.SH "SYNOPSIS"
+.
+.TP
+\fBcspice chronos\fR
+\fB\-setup\fR \fIfile\fR
+.
+.br
+\fB\-from\fR \fItime_system\fR
+.
+.br
+\fB\-to\fR \fItime_system\fR
+.
+.br
+\fB\-time\fR \fIinput_time\fR | \fB\-batch\fR
+.
+.br
+[\fIoptions\fR]
+.
+.SH "DESCRIPTION"
+\fBCHRONOS\fR is a utility program that converts time between various time systems\. It supports the following time systems:
+.
+.TP
+UTC
+Universal Time Coordinated; UTC is a system of time keeping that gives a name to each instant of time of the International Atomic Time system; refer to the NAIF Toolkit TIME\.REQ document for more discussion regarding UTC;
+.
+.TP
+ET
+Ephemeris Time; Ephemeris time is the uniform time scale represented by the independent variable in the differential equations that describe the motions of the planets, sun and moon\. CHRONOS deals with one of the two forms of ET \-\- Barycentric Dynamical Time (TDB) which is used when describing the motion of bodies with respect to the solar system barycenter; refer to the NAIF Toolkit TIME\.REQ document for more discussion regarding ET;
+.
+.TP
+SCLK
+Spacecraft On\-Board Clock Time; SCLK is the on\-board time\-keeping mechanism that triggers most spacecraft events and is the fundamental time measurement for referencing most spacecraft activities and instrument data; refer to the NAIF Toolkit SCLK\.REQ document for more discussion regarding SCLK;
+.
+.TP
+LST
+Local Solar Time; LST is simply a measure of angles between landing (sub\-spacecraft) and sub\-solar meridians on the surface of a body expressed as a "24 hour" local clock\.
+.
+.P
+\fBCHRONOS\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+Command line keys \'\-XXXXXXX\' are case insensitive\. Any of the command line options can be present in the command line multiple times (in such cases the last appearance of a key takes precedence\.) The order in which options are specified is insignificant\.
+.
+.TP
+\fB\-setup\fR \fIsetup_file\fR
+Specify a setup file name or directly list the names of the SPICE kernels to be used\. If \fIsetup_file\fR is not present or is blank, it tries to obtain it from the environment variable CHRONOS_SETUP_FILE\.
+.
+.TP
+\fB\-from\fR \fItime_system\fR
+Specify the time system of the input time\.
+.
+.TP
+\fB\-fromtype\fR \fItime_type\fR
+Specify the time type of the input time\. If it\'s not present or is blank, it is assumed the default time type for the input time system (SCET for UTC and ET, SCLK for SCLK, and LST for LST)\.
+.
+.TP
+\fB\-to\fR \fItime_system\fR
+Specify the time system of the output time\.
+.
+.TP
+\fB\-totype\fR \fItime_type\fR
+Specify the time type of the output time\. If it\'s not present or is blank, it is assumed the default time type for the output time system (SCET for UTC and ET, SCLK for SCLK and LST for LST)\.
+.
+.TP
+\fB\-format\fR \fIoutput_format\fR
+Specify a custom format for the output time\. If a format specification is not present or is blank, it looks for a specification in the setup file and, if such is also not available, it uses the default format\.
+.
+.TP
+\fB\-time\fR \fItime\fR
+Specify the input time\. Most time types of UTC and ET systems require input time to be in a form of a time string recognized by TIME subsystem of SPICE\.
+.
+.TP
+\fB\-batch\fR
+Tell the program to take input time(s) from standard input instead of the command line\. If it\'s present, the program ignores any input time provided after the \fB\-time\fR option\.
+.
+.TP
+\fB\-sc\fR \fIsc_id\fR
+Specify the NAIF ID for the spacecraft\. If \fIsc_id\fR is not present, the program looks for it in the setup file\.
+.
+.TP
+\fB\-center\fR \fIbody_id\fR
+Specify the NAIF ID for the center body\. If \fIbody_id\fR is not present, the program looks for it in the setup file\.
+.
+.TP
+\fB\-landingtime\fR \fItime\fR
+Specify the UTC time of the landing\. If \fItime\fR is not present, the program looks for it in the setup file\.
+.
+.TP
+\fB\-sol1index\fR \fIindex\fR
+Specify the SOL index for the first day on surface\. If \fIindex\fR is not present, the program looks for it in the setup file\.
+.
+.TP
+\fB\-nolabel\fR
+Tell the program to not display [SYSTEM]/[TYPE] following the output time string\.
+.
+.TP
+\fB\-trace\fR
+Tell the program to display trace information including, complete command line, names of the loaded SPICE kernel files, all relevant setup information, etc\. This option overrules the \fB\-nolabel\fR option\.
+.
+.TP
+\fB\-template\fR
+Display setup file template\.
+.
+.TP
+\fB\-h\fR, \fB\-help\fR
+Display help information\.
+.
+.TP
+\fB\-u\fR, \fB\-usage\fR
+Display usage information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-chronos.md b/debian/man/cspice-chronos.md
new file mode 100644
index 0000000..b21153d
--- /dev/null
+++ b/debian/man/cspice-chronos.md
@@ -0,0 +1,132 @@
+cspice-chronos(1) -- convert time from one supported system/type to another
+===========================================================================
+
+SYNOPSIS
+--------
+ * **cspice chronos**:
+ **-setup** _file_
+ **-from** _time_system_
+ **-to** _time_system_
+ **-time** _input_time_ | **-batch**
+ [_options_]
+
+DESCRIPTION
+-----------
+**CHRONOS** is a utility program that converts time between various time
+systems. It supports the following time systems:
+
+ * UTC:
+ Universal Time Coordinated; UTC is a system of time keeping that gives a
+ name to each instant of time of the International Atomic Time system;
+ refer to the NAIF Toolkit TIME.REQ document for more discussion
+ regarding UTC;
+
+ * ET:
+ Ephemeris Time; Ephemeris time is the uniform time scale represented by
+ the independent variable in the differential equations that describe the
+ motions of the planets, sun and moon. CHRONOS deals with one of the two
+ forms of ET -- Barycentric Dynamical Time (TDB) which is used when
+ describing the motion of bodies with respect to the solar system
+ barycenter; refer to the NAIF Toolkit TIME.REQ document for more
+ discussion regarding ET;
+
+ * SCLK:
+ Spacecraft On-Board Clock Time; SCLK is the on-board time-keeping
+ mechanism that triggers most spacecraft events and is the fundamental
+ time measurement for referencing most spacecraft activities and
+ instrument data; refer to the NAIF Toolkit SCLK.REQ document for more
+ discussion regarding SCLK;
+
+ * LST:
+ Local Solar Time; LST is simply a measure of angles between landing
+ (sub-spacecraft) and sub-solar meridians on the surface of a body
+ expressed as a "24 hour" local clock.
+
+**CHRONOS** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+Command line keys '-XXXXXXX' are case insensitive. Any of the command line
+options can be present in the command line multiple times (in such cases the
+last appearance of a key takes precedence.) The order in which options are
+specified is insignificant.
+
+ * `-setup` _setup_file_:
+ Specify a setup file name or directly list the names of the SPICE
+ kernels to be used. If _setup_file_ is not present or is blank, it tries
+ to obtain it from the environment variable CHRONOS_SETUP_FILE.
+
+ * `-from` _time_system_:
+ Specify the time system of the input time.
+
+ * `-fromtype` _time_type_:
+ Specify the time type of the input time. If it's not present or is
+ blank, it is assumed the default time type for the input time system
+ (SCET for UTC and ET, SCLK for SCLK, and LST for LST).
+
+ * `-to` _time_system_:
+ Specify the time system of the output time.
+
+ * `-totype` _time_type_:
+ Specify the time type of the output time. If it's not present or is
+ blank, it is assumed the default time type for the output time system
+ (SCET for UTC and ET, SCLK for SCLK and LST for LST).
+
+ * `-format` _output_format_:
+ Specify a custom format for the output time. If a format specification
+ is not present or is blank, it looks for a specification in the setup
+ file and, if such is also not available, it uses the default format.
+
+ * `-time` _time_:
+ Specify the input time. Most time types of UTC and ET systems require
+ input time to be in a form of a time string recognized by TIME subsystem
+ of SPICE.
+
+ * `-batch`:
+ Tell the program to take input time(s) from standard input instead of
+ the command line. If it's present, the program ignores any input time
+ provided after the **-time** option.
+
+ * `-sc` _sc_id_:
+ Specify the NAIF ID for the spacecraft. If _sc_id_ is not present, the
+ program looks for it in the setup file.
+
+ * `-center` _body_id_:
+ Specify the NAIF ID for the center body. If _body_id_ is not present,
+ the program looks for it in the setup file.
+
+ * `-landingtime` _time_:
+ Specify the UTC time of the landing. If _time_ is not present, the
+ program looks for it in the setup file.
+
+ * `-sol1index` _index_:
+ Specify the SOL index for the first day on surface. If _index_ is not
+ present, the program looks for it in the setup file.
+
+ * `-nolabel`:
+ Tell the program to not display [SYSTEM]/[TYPE] following the output
+ time string.
+
+ * `-trace`:
+ Tell the program to display trace information including, complete
+ command line, names of the loaded SPICE kernel files, all relevant setup
+ information, etc. This option overrules the **-nolabel** option.
+
+ * `-template`:
+ Display setup file template.
+
+ * `-h`, `-help`:
+ Display help information.
+
+ * `-u`, `-usage`:
+ Display usage information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-ckbrief.1 b/debian/man/cspice-ckbrief.1
index f3e1e2e..d60b14a 100644
--- a/debian/man/cspice-ckbrief.1
+++ b/debian/man/cspice-ckbrief.1
@@ -1,89 +1,97 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-CKBRIEF 1
-.SH NAME
-cspice-ckbrief \- displays a summary for binary CK files
-.SH SYNOPSIS
-.B cspice-ckbrief
-.RI [OPTIONS]
-.RI FILE
-[\fIFILE\fR ...]
-
-
-.SH DESCRIPTION
-.PP
-.B cspice-ckbrief
-displays a summary of the contents and time coverage for one or more binary CK files.
-It displays a summary for each CK file listed on the command line, in a list file, and/or a meta-kernel. It can display coverage boundaries as ephemeris time (ET) in calendar format, as UTC time in "year-month-day" or "day-of-year" format, or as on-board clock (SCLK) time in string or encoded format. It can display the summary in a variety of formats, with or without showing the names of the frames associated with spacecraft or structure IDs or the names/IDs of the frames with respect to [...]
-.PP
-In order for the program to display times in the default format or any other format (except encoded SCLK), both an LSK file and an SCLK file containing required time correlation data must be provided on the command line, in a list file (specified with the option \fB\-f\fR described later in this document), or in a meta-kernel file given on the command line or in the list file.
-.PP
-.B cspice-ckbrief
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-
-.SH OPTIONS
-.SS Options Controlling Output Summary Format
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-CKBRIEF" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-ckbrief\fR \- displays a summary for binary CK files
+.
+.SH "SYNOPSIS"
+\fBcspice ckbrief\fR [\fIoptions\fR] \fIfile\fR [\fIfile\fR \.\.\.]
+.
+.SH "DESCRIPTION"
+\fBCKBRIEF\fR is a command line program that displays a summary of the contents and time coverage for one or more binary CK files\. The program displays a summary for each CK file listed on the command line, in a list file, and/or a meta\-kernel\. It can display coverage boundaries as ephemeris time (ET) in calendar format, as UTC time in "year\-month\-day" or "day\-of\-year" format, or as on\-board clock (SCLK) time in string or encoded format\. It can display the summary in a variety o [...]
+.
+.P
+In order for the program to display times in the default format or any other format (except encoded SCLK), both an LSK file and an SCLK file containing required time correlation data must be provided on the command line, in a list file (specified with the option \fB\-f\fR described later in this document), or in a meta\-kernel file given on the command line or in the list file\.
+.
+.P
+\fBCKBRIEF\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+.
+.SS "Options Controlling Output Summary Format"
+.
.TP
-.BR \-dump
-Display a summary of interpolation interval boundaries, the actual time periods for which the file provides data, for each of the segments in the file.
+\fB\-dump\fR
+Display a summary of interpolation interval boundaries, the actual time periods for which the file provides data, for each of the segments in the file\.
+.
.TP
-.BR \-nm
-Display a summary of segment boundaries for each of the structures in the file.
-This option is ignored when \fB\-dump\fR is specified.
+\fB\-nm\fR
+Display a summary of segment boundaries for each of the structures in the file\. This option is ignored when \fB\-dump\fR is specified\.
+.
.TP
-.BR \-rel
-Display, in the additional right-hand column, frames with respect to which the orientation is given in the CK segments. For frames known to SPICE, built-in or defined in the FK files provided to the program along with CK, LSK, and SCLK files, the program displays names; for unrecognized frames, the program displays IDs.
-This option is ignored when \fB\-g\fR is specified.
+\fB\-rel\fR
+Display, in the additional right\-hand column, frames with respect to which the orientation is given in the CK segments\. For frames known to SPICE, built\-in or defined in the FK files provided to the program along with CK, LSK, and SCLK files, the program displays names; for unrecognized frames, the program displays IDs\. This option is ignored when \fB\-g\fR is specified\.
+.
.TP
-.BR \-n
-Display frame names associated with the structure IDs instead of the numeric structure IDs. For frames known to SPICE, defined in the FK files provided to the program, the program displays names; for unrecognized frames, the program displays IDs with the prefix "NO FRAME FOR <id>".
+\fB\-n\fR
+Display frame names associated with the structure IDs instead of the numeric structure IDs\. For frames known to SPICE, defined in the FK files provided to the program, the program displays names; for unrecognized frames, the program displays IDs with the prefix "NO FRAME FOR \fIid\fR"\.
+.
.TP
-.BR \-t
-Use the tabular display format in which coverage information for all structures from each file is presented in a single table with the structure IDs provided in the left column rather than in the table headers.
+\fB\-t\fR
+Use the tabular display format in which coverage information for all structures from each file is presented in a single table with the structure IDs provided in the left column rather than in the table headers\.
+.
.TP
-.BR \-g
-Use the grouping display format, in which information for structures with the same coverage is grouped together into blocks with the coverage begin and end time shown first, and the list of structure IDs shown below them.
-This option is ignored when \fB\-dump\fR or \fB\-t\fR are specified.
-
-.SS Options Controlling Output Time Format
-In order for the program to display times in the default format or any other format (except encoded SCLK), both an LSK file and an SCLK file containing required time correlation data must be provided.
-.PP
-When multiple options controlling the output time format are given at the same time, the option specified last on the command line takes precedence.
+\fB\-g\fR
+Use the grouping display format, in which information for structures with the same coverage is grouped together into blocks with the coverage begin and end time shown first, and the list of structure IDs shown below them\. This option is ignored when \fB\-dump\fR or \fB\-t\fR are specified\.
+.
+.SS "Options Controlling Output Time Format"
+In order for the program to display times in the default format or any other format (except encoded SCLK), both an LSK file and an SCLK file containing required time correlation data must be provided\.
+.
+.P
+When multiple options controlling the output time format are given at the same time, the option specified last on the command line takes precedence\.
+.
.TP
-.BR \-utc
-Display time tags as UTC in the "YYYY-MON-DD HR:MN:SC.DDD" format (needs LSK and SCLK).
+\fB\-utc\fR
+Display time tags as UTC in the "YYYY\-MON\-DD HR:MN:SC\.DDD" format (needs LSK and SCLK)\.
+.
.TP
-.BR \-utcdoy
-Display time tags as UTC times in the "YYYY-DOY // HR:MN:SC.DDD" format (needs LSK and SCLK).
+\fB\-utcdoy\fR
+Display time tags as UTC times in the "YYYY\-DOY // HR:MN:SC\.DDD" format (needs LSK and SCLK)\.
+.
.TP
-.BR \-sclk
-Display time tags as SCLK strings (needs LSK and SCLK).
+\fB\-sclk\fR
+Display time tags as SCLK strings (needs LSK and SCLK)\.
+.
.TP
-.BR \-dpsclk
-Display time tags as encoded SCLKs (ticks).
-
-.SS Miscellaneous Options
+\fB\-dpsclk\fR
+Display time tags as encoded SCLKs (ticks)\.
+.
+.SS "Miscellaneous Options"
+.
.TP
\fB\-a\fR
-Display a summary for multiple CKs listed on the command line and/or provided in meta-kernels and/or a list file as if all data from these CKs were provided in a single CK file.
+Display a summary for multiple CKs listed on the command line and/or provided in meta\-kernels and/or a list file as if all data from these CKs were provided in a single CK file\.
+.
.TP
-\fIID\fR
-One or more (up to 100) structure IDs may be listed on the command line to tell BRIEF to display summary information only for the specified structure(s).
+\fIid\fR
+One or more (up to 100) structure IDs may be listed on the command line to tell BRIEF to display summary information only for the specified structure(s)\.
+.
.TP
-\fB\-f\fR \fILIST_FILE\fR
-Display a summary for the files whose names are listed in the text file \fILIST_FILE\fR.
-The file names can be provided one-per-line or a few-per-line separated by one or more spaces.
+\fB\-f\fR \fIlist_file\fR
+Display a summary for the files whose names are listed in the text file \fIlist_file\fR\. The file names can be provided one\-per\-line or a few\-per\-line separated by one or more spaces\.
+.
.TP
\fB\-h\fR
-Display a complete usage message listing all options and exit.
+Display a complete usage message listing all options and exit\.
+.
.TP
\fB\-v\fR
-Display just the version line and exit.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+Display just the version line and exit\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-ckbrief.md b/debian/man/cspice-ckbrief.md
new file mode 100644
index 0000000..4a6f55c
--- /dev/null
+++ b/debian/man/cspice-ckbrief.md
@@ -0,0 +1,123 @@
+cspice-ckbrief(1) -- displays a summary for binary CK files
+===========================================================
+
+SYNOPSIS
+--------
+**cspice ckbrief** [_options_] _file_ [_file_ ...]
+
+DESCRIPTION
+-----------
+**CKBRIEF** is a command line program that displays a summary of the
+contents and time coverage for one or more binary CK files. The program
+displays a summary for each CK file listed on the command line, in a list
+file, and/or a meta-kernel. It can display coverage boundaries as ephemeris
+time (ET) in calendar format, as UTC time in "year-month-day" or
+"day-of-year" format, or as on-board clock (SCLK) time in string or encoded
+format. It can display the summary in a variety of formats, with or without
+showing the names of the frames associated with spacecraft or structure IDs
+or the names/IDs of the frames with respect to which orientation is provided.
+
+In order for the program to display times in the default format or any other
+format (except encoded SCLK), both an LSK file and an SCLK file containing
+required time correlation data must be provided on the command line, in a
+list file (specified with the option **-f** described later in this
+document), or in a meta-kernel file given on the command line or in the list
+file.
+
+**CKBRIEF** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+### Options Controlling Output Summary Format
+
+ * `-dump`:
+ Display a summary of interpolation interval boundaries, the actual time
+ periods for which the file provides data, for each of the segments in
+ the file.
+
+ * `-nm`:
+ Display a summary of segment boundaries for each of the structures in
+ the file. This option is ignored when **-dump** is specified.
+
+ * `-rel`:
+ Display, in the additional right-hand column, frames with respect to
+ which the orientation is given in the CK segments. For frames known to
+ SPICE, built-in or defined in the FK files provided to the program along
+ with CK, LSK, and SCLK files, the program displays names; for
+ unrecognized frames, the program displays IDs. This option is ignored
+ when **-g** is specified.
+
+ * `-n`:
+ Display frame names associated with the structure IDs instead of the
+ numeric structure IDs. For frames known to SPICE, defined in the FK
+ files provided to the program, the program displays names; for
+ unrecognized frames, the program displays IDs with the prefix "NO FRAME
+ FOR <id>".
+
+ * `-t`:
+ Use the tabular display format in which coverage information for all
+ structures from each file is presented in a single table with the
+ structure IDs provided in the left column rather than in the table
+ headers.
+
+ * `-g`:
+ Use the grouping display format, in which information for structures
+ with the same coverage is grouped together into blocks with the coverage
+ begin and end time shown first, and the list of structure IDs shown
+ below them. This option is ignored when **-dump** or **-t** are specified.
+
+### Options Controlling Output Time Format
+
+In order for the program to display times in the default format or any other
+format (except encoded SCLK), both an LSK file and an SCLK file containing
+required time correlation data must be provided.
+
+When multiple options controlling the output time format are given at the
+same time, the option specified last on the command line takes precedence.
+
+ * `-utc`:
+ Display time tags as UTC in the "YYYY-MON-DD HR:MN:SC.DDD" format (needs
+ LSK and SCLK).
+
+ * `-utcdoy`:
+ Display time tags as UTC times in the "YYYY-DOY // HR:MN:SC.DDD" format
+ (needs LSK and SCLK).
+
+ * `-sclk`:
+ Display time tags as SCLK strings (needs LSK and SCLK).
+
+ * `-dpsclk`:
+ Display time tags as encoded SCLKs (ticks).
+
+### Miscellaneous Options
+
+ * `-a`:
+ Display a summary for multiple CKs listed on the command line and/or
+ provided in meta-kernels and/or a list file as if all data from these
+ CKs were provided in a single CK file.
+
+ * _id_:
+ One or more (up to 100) structure IDs may be listed on the command line
+ to tell BRIEF to display summary information only for the specified
+ structure(s).
+
+ * `-f` _list_file_:
+ Display a summary for the files whose names are listed in the text file
+ _list_file_. The file names can be provided one-per-line or a
+ few-per-line separated by one or more spaces.
+
+ * `-h`:
+ Display a complete usage message listing all options and exit.
+
+ * `-v`:
+ Display just the version line and exit.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-commnt.1 b/debian/man/cspice-commnt.1
index 0fe037b..49d0a43 100644
--- a/debian/man/cspice-commnt.1
+++ b/debian/man/cspice-commnt.1
@@ -1,50 +1,63 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-COMMNT 1
-.SH NAME
-cspice-commnt \- manipulate comments from SPICE binary kernel files
-.SH SYNOPSIS
-.B cspice-commnt
-.br
-.B cspice-commnt
-[\fIOPTIONS\fR]
-.br
-.B cspice-commnt
-\fB\-a\fR | \fB\-e\fR \fIKERNEL_FILE\fR \fICOMMENT_FILE\fR
-.br
-.B cspice-commnt
-\fB\-r\fR | \fB\-d\fR \fIKERNEL_FILE\fR
-
-.SH DESCRIPTION
-\fBcspice-commnt\fR
-is a program that reads, adds, extracts, or deletes comments from SPICE binary kernel files.
-.PP
-.B cspice-commnt
-can be used as a menu driven interactive program or as a command line utility.
-.PP
-.B cspice-commnt
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
-.TP
-\fB\-a\fR \fIKERNEL_FILE\fR \fICOMMENT_FILE\fR
-Add comments to a kernel file from a text file.
-.TP
-\fB\-e\fR \fIKERNEL_FILE\fR \fICOMMENT_FILE\fR
-Extract comments from a kernel file to a text file.
-.TP
-\fB\-r\fR \fIKERNEL_FILE\fR
-Read the comments in a kernel file, displaying the results on the Standard Output.
-.TP
-\fB\-d\fR \fIKERNEL_FILE\fR
-Delete all of the comments in a kernel file.
-.TP
-\fB\-h\fR
-Display usage information.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-COMMNT" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-commnt\fR \- manipulate comments from SPICE binary kernel files
+.
+.SH "SYNOPSIS"
+\fBcspice commnt\fR
+.
+.br
+\fBcspice commnt\fR \fB\-h\fR
+.
+.br
+\fBcspice commnt\fR \fB\-a\fR | \fB\-e\fR \fIkernel_file\fR \fIcomment_file\fR
+.
+.br
+\fBcspice commnt\fR \fB\-r\fR | \fB\-d\fR \fIkernel_file\fR
+.
+.SH "DESCRIPTION"
+The COMMNT utility program provides a collection of services useful for manipulating and examining the contents of the comment area in SPICE binary kernel files\. The COMMNT program can add comments to the comment area from a text file, read the comment area, displaying the comments on the terminal screen, extract the comment area to a text file, or delete the entire comment area of a SPICE binary kernel file\.
+.
+.P
+COMMNT can be used as a menu driven interactive program or as a command line utility\.
+.
+.P
+The COMMNT program supports the CK, DSK, EK, PCK, and SPK SPICE binary kernel file formats\.
+.
+.P
+The comments are stored in a "what you put in is what you get out" fashion, so care should be taken when formatting the comments before placing them into the comment area of a SPICE binary kernel file\.
+.
+.P
+\fBCOMMNT\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+To use COMMNT as a menu driven interactive program, run the program without any arguments\.
+.
+.TP
+\fB\-a\fR \fIkernel_file\fR \fIcomment_file\fR
+Add comments to a kernel file from a text file\.
+.
+.TP
+\fB\-e\fR \fIkernel_file\fR \fIcomment_file\fR
+Extract comments from a kernel file to a text file\.
+.
+.TP
+\fB\-r\fR \fIkernel_file\fR
+Read the comments in a kernel file, displaying the results on the Standard Output\.
+.
+.TP
+\fB\-d\fR \fIkernel_file\fR
+Delete all of the comments in a kernel file\.
+.
+.TP
+\fB\-h\fR
+Display usage information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-commnt.md b/debian/man/cspice-commnt.md
new file mode 100644
index 0000000..25eea35
--- /dev/null
+++ b/debian/man/cspice-commnt.md
@@ -0,0 +1,60 @@
+cspice-commnt(1) -- manipulate comments from SPICE binary kernel files
+======================================================================
+
+SYNOPSIS
+--------
+`cspice commnt`
+`cspice commnt` **-h**
+`cspice commnt` **-a** | **-e** _kernel_file_ _comment_file_
+`cspice commnt` **-r** | **-d** _kernel_file_
+
+DESCRIPTION
+-----------
+The COMMNT utility program provides a collection of services useful for
+manipulating and examining the contents of the comment area in SPICE
+binary kernel files. The COMMNT program can add comments to the comment
+area from a text file, read the comment area, displaying the comments on
+the terminal screen, extract the comment area to a text file, or delete
+the entire comment area of a SPICE binary kernel file.
+
+COMMNT can be used as a menu driven interactive program or as a command line
+utility.
+
+The COMMNT program supports the CK, DSK, EK, PCK, and SPK SPICE binary
+kernel file formats.
+
+The comments are stored in a "what you put in is what you get out"
+fashion, so care should be taken when formatting the comments before
+placing them into the comment area of a SPICE binary kernel file.
+
+**COMMNT** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+To use COMMNT as a menu driven interactive program, run the program without any arguments.
+
+ * `-a` _kernel_file_ _comment_file_:
+ Add comments to a kernel file from a text file.
+
+ * `-e` _kernel_file_ _comment_file_:
+ Extract comments from a kernel file to a text file.
+
+ * `-r` _kernel_file_:
+ Read the comments in a kernel file, displaying the results on the
+ Standard Output.
+
+ * `-d` _kernel_file_:
+ Delete all of the comments in a kernel file.
+
+ * `-h`:
+ Display usage information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-dskbrief.1 b/debian/man/cspice-dskbrief.1
new file mode 100644
index 0000000..328caaa
--- /dev/null
+++ b/debian/man/cspice-dskbrief.1
@@ -0,0 +1,90 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-DSKBRIEF" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-dskbrief\fR \- displays a summary for binary DSK files
+.
+.SH "SYNOPSIS"
+\fBcspice dskbrief\fR [\fIoptions\fR] \fIfile\fR [\fIfile\fR \.\.\.]
+.
+.SH "DESCRIPTION"
+\fBDSKBRIEF\fR displays a summary of the spatial coverage and additional attributes of one or more binary Digital Shape Kernel (DSK) files\.
+.
+.P
+A DSK summary includes at a minimum:
+.
+.IP "\(bu" 4
+The names or ID codes of the body or bodies for which the DSK provides data
+.
+.IP "\(bu" 4
+The surface names or surface ID codes associated with the bodies (see the DSK Required Reading, dsk\.req, for a discussion of surfaces\.)
+.
+.IP "\(bu" 4
+The names or ID codes of the reference frames relative to which DSK data are expressed
+.
+.IP "\(bu" 4
+The coordinate systems used to describe spatial coverage
+.
+.IP "\(bu" 4
+The bounds of the spatial regions for which the DSK provides data
+.
+.IP "" 0
+.
+.P
+Coverage for multiple DSK segments and files can be aggregated and displayed as though the DSK data were contained in a single file\.
+.
+.P
+The user can command \fBDSKBRIEF\fR to produce detailed summaries, including summaries of individual DSK segments\. See the Usage section and the command examples below\.
+.
+.P
+An LSK file must be provided on the command line to display times in UTC formats\. FK file(s) must be provided on the command line to display names of any frames that are not built into the Toolkit\.
+.
+.P
+\fBDSKBRIEF\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+The options can be provided in any order and can appear before, after, or intermixed with file names\. The case of option keys is significant: they must be lowercase as shown below\.
+.
+.TP
+\fB\-a\fR
+Treat all DSK files as a single file\. This option has no effect when either \fB\-full\fR or \fB\-seg\fR is used\.
+.
+.TP
+\fB\-gaps\fR
+Display coverage gaps\. This option applies to sets of DSK files only when \fB\-a\fR is used\. It applies to sets of matching segments within a given DSK file unless \fB\-full\fR or \fB\-seg\fR are used\.
+.
+.TP
+\fB\-ext\fR
+Display extended summaries: in addition to the default set of attributes, these include data type, data class, and time bounds\. This option applies to summaries of groups of DSK segments\. This option has no effect when either \fB\-full\fR or \fB\-seg\fR is used\.
+.
+.TP
+\fB\-seg\fR
+Display a segment\-by\-segment summary\. This option overrides \fB\-a\fR\.
+.
+.TP
+\fB\-full\fR
+Display a detailed summary for each segment, including data\-type\-specific parameters\. This option implies a segment\-by\-segment summary\. This option overrides \fB\-a\fR\.
+.
+.TP
+\fB\-d\fR \fIn\fR
+Display \fIn\fR significant digits of floating point values\. The range of n is 3:17\.
+.
+.TP
+\fB\-v\fR
+Display the version of this program\.
+.
+.TP
+\fB\-h\fR
+Display help text\.
+.
+.TP
+\fB\-u\fR
+Display usage text\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on http://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-dskbrief.md b/debian/man/cspice-dskbrief.md
new file mode 100644
index 0000000..3f61a01
--- /dev/null
+++ b/debian/man/cspice-dskbrief.md
@@ -0,0 +1,89 @@
+cspice-dskbrief(1) -- displays a summary for binary DSK files
+=============================================================
+
+SYNOPSIS
+--------
+**cspice dskbrief** [_options_] _file_ [_file_ ...]
+
+DESCRIPTION
+-----------
+**DSKBRIEF** displays a summary of the spatial coverage and additional
+attributes of one or more binary Digital Shape Kernel (DSK) files.
+
+A DSK summary includes at a minimum:
+
+ * The names or ID codes of the body or bodies for which the DSK provides data
+
+ * The surface names or surface ID codes associated with the bodies (see the
+ DSK Required Reading, dsk.req, for a discussion of surfaces.)
+
+ * The names or ID codes of the reference frames relative to which DSK data are
+ expressed
+
+ * The coordinate systems used to describe spatial coverage
+
+ * The bounds of the spatial regions for which the DSK provides data
+
+Coverage for multiple DSK segments and files can be aggregated and displayed as
+though the DSK data were contained in a single file.
+
+The user can command **DSKBRIEF** to produce detailed summaries,
+including summaries of individual DSK segments. See the Usage section and the
+command examples below.
+
+An LSK file must be provided on the command line to display times in UTC
+formats. FK file(s) must be provided on the command line to display names of
+any frames that are not built into the Toolkit.
+
+**DSKBRIEF** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+The options can be provided in any order and can appear before, after, or
+intermixed with file names. The case of option keys is significant: they must
+be lowercase as shown below.
+
+ * `-a`:
+ Treat all DSK files as a single file. This option has no effect when either
+ **-full** or **-seg** is used.
+
+ * `-gaps`:
+ Display coverage gaps. This option applies to sets of DSK files only when
+ **-a** is used. It applies to sets of matching segments within a given DSK
+ file unless **-full** or **-seg** are used.
+
+ * `-ext`:
+ Display extended summaries: in addition to the default set of attributes,
+ these include data type, data class, and time bounds. This option applies
+ to summaries of groups of DSK segments. This option has no effect when
+ either **-full** or **-seg** is used.
+
+ * `-seg`:
+ Display a segment-by-segment summary. This option overrides **-a**.
+
+ * `-full`:
+ Display a detailed summary for each segment, including data-type-specific
+ parameters. This option implies a segment-by-segment summary. This option
+ overrides **-a**.
+
+ * `-d` _n_:
+ Display _n_ significant digits of floating point values. The range of n is
+ 3:17.
+
+ * `-v`:
+ Display the version of this program.
+
+ * `-h`:
+ Display help text.
+
+ * `-u`:
+ Display usage text.
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-dskexp.1 b/debian/man/cspice-dskexp.1
new file mode 100644
index 0000000..d88218b
--- /dev/null
+++ b/debian/man/cspice-dskexp.1
@@ -0,0 +1,213 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-DSKEXP" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-dskexp\fR \- exports data from DSK files to text files
+.
+.SH "SYNOPSIS"
+.
+.TP
+\fBcspice dskexp\fR
+\fB\-dsk\fR \fIdsk\fR \fB\-text\fR \fIoutput_name\fR \fB\-format\fR \fIformat\fR [\fB\-prec\fR \fIn\fR]
+.
+.SH "DESCRIPTION"
+\fBDSKEXP\fR enables SPICE Toolkit users to "export" data from a DSK file to any of a variety of simple, easily parsed text formats\. This capability enables users to easily transform DSK files into formats required by other applications; it also makes it easy to inspect the data in a DSK file\.
+.
+.P
+\fBDSKEXP\fR currently is limited to processing type 2 (plate model) DSK segments\.
+.
+.P
+If the input DSK file contains multiple segments, an output text file will be created for each segment\.
+.
+.P
+\fBDSKEXP\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OUTPUT FORMATS"
+The supported formats are:
+.
+.IP "1." 4
+\fIplate\-vertex\fR table\. The format code for this format is \fI1\fR\. The output file format is:
+.
+.IP "" 4
+.
+.nf
+
+<vertex count NV>
+1 <vertex 1 X value><Y value><Z value>
+ \.\.\.
+NV <vertex NV X value><Y value><Z value>
+<plate count NP>
+1 <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ \.\.\.
+NP <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+.
+.fi
+.
+.IP "" 0
+
+.
+.IP "2." 4
+\fIvertex\-facet\fR table\. This format is also called \fIobj\fR format\. The format code for this format is \fI3\fR\. The output file format is:
+.
+.IP "" 4
+.
+.nf
+
+v <vertex 1 X value><Y value><Z value>
+ \.\.\.
+v <vertex NV X value><Y value><Z value>
+f <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ \.\.\.
+f <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+.
+.fi
+.
+.IP "" 0
+
+.
+.IP "3." 4
+Rosetta/OSIRIS \fIver\fR format\. The format code for this format is \fI4\fR\. The output file format is:
+.
+.IP "" 4
+.
+.nf
+
+<vertex count NV> <plate count NP>
+ <vertex 1 X value><Y value><Z value>
+ \.\.\.
+ <vertex NV X value><Y value><Z value>
+3
+ <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ \.\.\.
+3
+ <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+.
+.fi
+.
+.IP "" 0
+
+.
+.IP "" 0
+.
+.P
+In the diagram above, NV and NP are the vertex and plate counts, respectively\.
+.
+.P
+The Gaskell ICQ format (format code 2) is not supported as an export format\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-dsk\fR \fIdsk\fR
+Specify DSK input file\.
+.
+.TP
+\fB\-text\fR \fItext\fR
+Specify output text file\. If the input file contains multiple segments, an output file will be written for each segment\. The file for the nth segment, where n is greater than 1, will have the string "_\fIn\-1\fR" appended to the output file name specified on the command line\. For example, if the input DSK contains multiple segments and if the specified output file name is \'phobos\.plt\' then the file for the first segment will have that name, the file for the second segment will be n [...]
+.
+.TP
+\fB\-format\fR \fIformat\fR
+Specifies the output file format\. Output formats may be specified by name or by integer code\. All of the supported output formats are valid \fBcspice\-mkdsk\fR input file formats\. See the section "OUTPUT FORMATS" above for further information\.
+.
+.TP
+\fB\-prec\fR \fIn\fR
+The optional output precision specification allows users to limit the precision of the double precision numbers representing components of plate model vertices\. Reducing the output precision can significantly reduce the size of the output file\. By default, full precision (17 mantissa digits) is used\. Range is 1:17\.
+.
+.SH "EXAMPLES"
+Create a vertex\-facet format output file\. This example uses default precision for the output vertices:
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format vertex\-facet
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a vertex\-facet format output file\. Use 9\-digit mantissas for the vertices\. The format name "obj" can be used to indicate vertex\-facet format\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format obj \-prec 9
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a vertex\-facet format output file\. Use 9\-digit mantissas for the vertices\. The format code 3 can be used to indicate vertex\-facet format\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format 3 \-prec 9
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a plate\-vertex format output file\. This example uses default precision for the output vertices\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format plate\-vertex
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a plate\-vertex format output file\. Use the integer code for this format\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format 1
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a Rosetta "ver" format output file\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format ver
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Create a Rosetta "ver" format output file\. Use the integer code for this format\.
+.
+.IP "" 4
+.
+.nf
+
+cspice dskexp \-dsk phobos\.bds \-text phobos\.obj \-format 4
+.
+.fi
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7), \fBcspice\-mkdsk\fR(1)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-dskexp.md b/debian/man/cspice-dskexp.md
new file mode 100644
index 0000000..f5d21a5
--- /dev/null
+++ b/debian/man/cspice-dskexp.md
@@ -0,0 +1,145 @@
+cspice-dskexp(1) -- exports data from DSK files to text files
+=============================================================
+
+SYNOPSIS
+--------
+ * **cspice dskexp**:
+ **-dsk** _dsk_
+ **-text** _output_name_
+ **-format** _format_
+ [**-prec** _n_]
+
+
+DESCRIPTION
+-----------
+**DSKEXP** enables SPICE Toolkit users to "export" data from a DSK file
+to any of a variety of simple, easily parsed text formats. This capability
+enables users to easily transform DSK files into formats required by other
+applications; it also makes it easy to inspect the data in a DSK file.
+
+**DSKEXP** currently is limited to processing type 2 (plate model) DSK
+segments.
+
+If the input DSK file contains multiple segments, an output text file will be
+created for each segment.
+
+**DSKEXP** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OUTPUT FORMATS
+--------------
+The supported formats are:
+
+ 1. _plate-vertex_ table. The format code for this format is _1_. The output
+ file format is:
+
+ <vertex count NV>
+ 1 <vertex 1 X value><Y value><Z value>
+ ...
+ NV <vertex NV X value><Y value><Z value>
+ <plate count NP>
+ 1 <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ ...
+ NP <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+
+ 2. _vertex-facet_ table. This format is also called _obj_ format. The format
+ code for this format is _3_. The output file format is:
+
+ v <vertex 1 X value><Y value><Z value>
+ ...
+ v <vertex NV X value><Y value><Z value>
+ f <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ ...
+ f <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+
+
+
+ 3. Rosetta/OSIRIS _ver_ format. The format code for this format is _4_. The
+ output file format is:
+
+ <vertex count NV> <plate count NP>
+ <vertex 1 X value><Y value><Z value>
+ ...
+ <vertex NV X value><Y value><Z value>
+ 3
+ <plate 1 vertex 1 ID><vertex 2 ID><vertex 3 ID>
+ ...
+ 3
+ <plate NP vertex 1 ID><vertex 2 ID><vertex 3 ID>
+
+In the diagram above, NV and NP are the vertex and plate counts, respectively.
+
+The Gaskell ICQ format (format code 2) is not supported as an export format.
+
+
+OPTIONS
+-------
+ * `-dsk` _dsk_:
+ Specify DSK input file.
+
+ * `-text` _text_:
+ Specify output text file. If the input file contains multiple segments,
+ an output file will be written for each segment. The file for the nth
+ segment, where n is greater than 1, will have the string "_<n-1>"
+ appended to the output file name specified on the command line. For
+ example, if the input DSK contains multiple segments and if the specified
+ output file name is 'phobos.plt' then the file for the first segment will
+ have that name, the file for the second segment will be named
+ 'phobos.plt_1' and so on.
+
+ * `-format` _format_:
+ Specifies the output file format. Output formats may be specified by
+ name or by integer code. All of the supported output formats are valid
+ **cspice-mkdsk** input file formats. See the section "OUTPUT FORMATS"
+ above for further information.
+
+ * `-prec` _n_:
+ The optional output precision specification allows users to limit the
+ precision of the double precision numbers representing components of
+ plate model vertices. Reducing the output precision can significantly
+ reduce the size of the output file. By default, full precision (17
+ mantissa digits) is used. Range is 1:17.
+
+EXAMPLES
+--------
+Create a vertex-facet format output file. This example uses default
+precision for the output vertices:
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format vertex-facet
+
+Create a vertex-facet format output file. Use 9-digit mantissas for the
+vertices. The format name "obj" can be used to indicate vertex-facet format.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format obj -prec 9
+
+Create a vertex-facet format output file. Use 9-digit mantissas for the
+vertices. The format code 3 can be used to indicate vertex-facet format.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format 3 -prec 9
+
+Create a plate-vertex format output file. This example uses default precision
+for the output vertices.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format plate-vertex
+
+Create a plate-vertex format output file. Use the integer code for this format.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format 1
+
+Create a Rosetta "ver" format output file.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format ver
+
+Create a Rosetta "ver" format output file. Use the integer code for this
+format.
+
+ cspice dskexp -dsk phobos.bds -text phobos.obj -format 4
+
+
+SEE ALSO
+--------
+**cspice**(7), **cspice-mkdsk**(1)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-frmdiff.1 b/debian/man/cspice-frmdiff.1
index cc2f1ed..623cd04 100644
--- a/debian/man/cspice-frmdiff.1
+++ b/debian/man/cspice-frmdiff.1
@@ -1,135 +1,164 @@
-.TH CSPICE-FRMDIFF 1
-.SH NAME
-cspice-frmdiff \- compute differences between two reference frames
-.SH SYNOPSIS
-\fBcspice-frmdiff\fR [\fIOPTIONS\fR] \fIFIRST_KERNEL\fR \fISECOND_KERNEL\fR
-.br
-\fBcspice-frmdiff\fR [\fIOPTIONS\fR] \fIKERNEL\fR
-.br
-\fBcspice-frmdiff\fR [\fIOPTIONS\fR]
-
-.SH DESCRIPTION
-.B cspice-frmdiff
-provides means for sampling orientation of a single reference frame, or for comparing orientations of two reference frames known to SPICE and supported by data from SPICE kernels.
-.PP
-To sample orientation of a single frame the program computes a set of transformations from one frame (the "from" frame) to another frame (the "to" frame) over an interval of time with fixed or variable time step, using a given set of kernel files. Then, depending on the requested type of output report, it prints to the screen a table containing these transformations expressed as total rotation angles and axes, quaternions, matrices or Euler angles and angular velocities, or only magnitud [...]
-.PP
-To compare orientations of two frames the program computes a set of transformations from one frame (the "from" frame) to another frame (the "to" frame) over an interval of time with a fixed or variable time step using one set of kernels, computes a set of transformations for the same or a different "from"-"to" frame combination at the same times using the same or a different set of kernels, and then computes the difference in rotation and angular velocity between the corresponding transf [...]
-.PP
-.B cspice-frmdiff
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
-.TP
-\fB\-k\fR \fIKERNEL\fR ...
-Specify the list of additional kernels that should be used for both frame transformations to be computed.
-Kernel names must be separated by spaces.
-.TP
-\fB\-f1\fR \fIFRAME\fR
-Specify the "from" frame for the first (or only) frame transformation to be computed. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID.
-.TP
-\fB\-t1\fR \fIFRAME\fR
-Specify the "to" frame for the first (or only) frame transformation to be computed. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID.
-.TP
-\fB\-c1\fR \fIFRAME\fR
-Specify the "coverage" frame to be used to look up the first coverage window. This frame must be known to SPICE and must be either a PCK-based (Class 2) or CK-based (Class 3) frame. It can be specified using the frame name, frame ID, or, if the first (or only) primary kernel is a CK or a binary PCK, class ID. If the first (or only) primary kernel file is a CK or a binary PCK, it must contain data for this frame.
-.TP
-\fB\-k1\fR \fIKERNEL\fR ...
-Specify the list of additional kernels that should be used only for the first frame transformation to be computed. Kernel names must be separated by spaces.
-.TP
-\fB\-f2\fR \fIFRAME\fR
-Specify the "from" frame for the second (or only) frame transformation to be computed. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID.
-.TP
-\fB\-t2\fR \fIFRAME\fR
-Specify the "to" frame for the second (or only) frame transformation to be computed. This frame must be known to SPICE and can be specified using the name, ID, or class ID.
-.TP
-\fB\-c2\fR \fIFRAME\fR
-Specify the "coverage" frame to be used to look up the second coverage window. This frame must be known to SPICE and must be either a PCK-based (Class 2) or CK-based (Class 3) frame. It can be specified using the frame name, frame ID, or, if the second (or only) primary kernel is a CK or a binary PCK, class ID. If the second (or only) primary kernel file is a CK or a binary PCK, it must contain data for this frame.
-.TP
-\fB\-k2\fR \fIKERNEL\fR ...
-Specify the list of additional kernels that should be used only for the second frame transformation to be computed. Kernel names must be separated by spaces.
-.TP
-\fB\-b\fR \fITIME\fR
-Specify the coverage window begin time. This option must be provided when no primary kernels and "coverage" frames are specified. The time string provided using this option can be in any form accepted by SPICE.
-.TP
-\fB\-e\fR \fITIME\fR
-Specify the coverage window end time. This option must be provided when no primary kernels and "coverage" frames are specified. The time string provided using this option can be in any form accepted by SPICE.
-.TP
-\fB\-n\fR \fINUMBER\fR
-Specify the number of points within the coverage window, for which the frame transformation(s) must be computed. The number must be an integer between 1 and 1,000,000. The default value is 1000.
-.TP
-\fB\-s\fR \fISTEP\fR
-specify the step, in seconds, for determining points within the coverage window, for which the frame transformation(s) must be computed. The step must be greater than 1E-8.
-This option supersedes \fB\-n\fR.
-.TP
-\fB\-t\fR \fIREPORT_TYPE\fR
-Specify the type of report that the program should display.
-.br
-By default, \fIREPORT_TYPE\fR is \fBbasic\fR, which means it will display only the maximum rotation angle and angular velocity (AV) magnitude.
-.br
-If \fIREPORT_TYPE\fR is \fBstats\fR, it will display statistics on rotation angles and AVs.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpaa\fR, it will display a table of rotation angles and axes.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpm\fR, it will display a table of matrices.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpqs\fR, it will display a table of SPICE-style quaternions.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpqo\fR, it will display a table of "other"-style quaternions.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpea\fR, it will display a table of Euler angles.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpc\fR, it will display a table of coverage intervals.
-.br
-If \fIREPORT_TYPE\fR is \fBdumpg\fR, it will display a table of coverage gaps.
-.TP
-\fB\-a\fR \fIAV_FLAG\fR
-Tell the program whether angular velocities should be computed along with rotations.
-.br
-By default, \fIAV_FLAG\fR is \fBno\fR, which means that only rotations are computed.
-.br
-If \fIAV_FLAG\fR is \fByes\fR, rotations and angular velocities are computed.
-.TP
-\fB\-m\fR \fIAV_FRAME\fR
-Tell the program in which frame angular velocities should be reported.
-.br
-By default, \fIAV_FRAME\fR is \fBfrom\fR, which means it will output angular velocities in "from" frame.
-.br
-If \fIAV_FRAME\fR is \fBto\fR, it will output angular velocities in "to" frame.
-.TP
-\fB\-f\fR \fITIME_TYPE\fR
-Specify the type of time tag to be used in tabular reports.
-.br
-By default, \fITIME_TYPE\fR is \fBet\fR, which means it will display times as TDB seconds past J2000.
-.br
-If \fITIME_TYPE\fR is \fBsclk\fR, it will display times as string SCLKs.
-.br
-If \fITIME_TYPE\fR is \fBsclkd\fR, it will display times as decimal SCLKs.
-.br
-If \fITIME_TYPE\fR is \fBticks\fR, it will display times as encoded SCLK ticks.
-.br
-If \fITIME_TYPE\fR is \fIPICT\fR, it will display times in any time format picture accepted by SPICE (for example "YYYY-MM-DDTHR:MN:SC.### ::RND" for time tags for be displayed as UTCs in ISO date format)
-.TP
-\fB\-o\fR \fIAXE\fR ...
-Specify the list of axes determining the order of rotations used for converting rotation matrices to Euler angles. The value must be a space-delimited list of three axes from the set of "X", "Y", "Z" (case-insensitive). The second axis must differ from the first and third axes. The default order is "Z Y X".
-.TP
-\fB\-x\fR \fIUNIT\fR
-Specify the units for the angles in the rotation angle and axis dump (\fB\-t dumpaa\fR) and Euler angle dump (\fB\-t dumpea\fR) reports; ignored for all other report types. Supported units are: \fBradians\fR (by default), \fBdegrees\fR, \fBarcminutes\fR, \fBarcseconds\fR, \fBhourangle\fR, \fBminuteangle\fR and \fBsecondangle\fR.
-.TP
-\fB\-d\fR \fINUMBER\fR
-Specify the number of significant digits in the output numeric times (TDB seconds past J2000, decimal SCLKs and encoded SCLK ticks) and rotation component values or rotation difference component values included in the dump, coverage and coverage gap reports. The number must be an integer between 6 and 17. The default value is 14.
-.TP
-\fB\-v\fR
-Display only the version line. This option overrides all other options.
-.TP
-\fB\-u\fR
-Display the usage message. This option overrides all other options except \fB\-v\fR.
-.TP
-\fB\-h\fR
-Display a brief help message. This option overrides all other options except \fB\-v\fR and \fB\-u\fR.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-FRMDIFF" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-frmdiff\fR \- compute differences between two reference frames
+.
+.SH "SYNOPSIS"
+\fBcspice frmdiff\fR [\fIoptions\fR] \fIfirst_kernel\fR \fIsecond_kernel\fR
+.
+.br
+\fBcspice frmdiff\fR [\fIoptions\fR] \fIkernel\fR
+.
+.br
+\fBcspice frmdiff\fR [\fIoptions\fR]
+.
+.SH "DESCRIPTION"
+\fBFRMDIFF\fR provides means for sampling orientation of a single reference frame, or for comparing orientations of two reference frames known to SPICE and supported by data from SPICE kernels\.
+.
+.P
+To sample orientation of a single frame the program computes a set of transformations from one frame (the "from" frame) to another frame (the "to" frame) over an interval of time with fixed or variable time step, using a given set of kernel files\. Then, depending on the requested type of output report, it prints to the screen a table containing these transformations expressed as total rotation angles and axes, quaternions, matrices or Euler angles and angular velocities, or only magnitu [...]
+.
+.P
+To compare orientations of two frames the program computes a set of transformations from one frame (the "from" frame) to another frame (the "to" frame) over an interval of time with a fixed or variable time step using one set of kernels, computes a set of transformations for the same or a different "from"\-"to" frame combination at the same times using the same or a different set of kernels, and then computes the difference in rotation and angular velocity between the corresponding trans [...]
+.
+.P
+\fBFRMDIFF\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-k\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels that should be used for both frame transformations to be computed\. Kernel names must be separated by spaces\.
+.
+.TP
+\fB\-f1\fR \fIframe\fR
+Specify the "from" frame for the first (or only) frame transformation to be computed\. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID\.
+.
+.TP
+\fB\-t1\fR \fIframe\fR
+Specify the "to" frame for the first (or only) frame transformation to be computed\. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID\.
+.
+.TP
+\fB\-c1\fR \fIframe\fR
+Specify the "coverage" frame to be used to look up the first coverage window\. This frame must be known to SPICE and must be either a PCK\-based (Class 2) or CK\-based (Class 3) frame\. It can be specified using the frame name, frame ID, or, if the first (or only) primary kernel is a CK or a binary PCK, class ID\. If the first (or only) primary kernel file is a CK or a binary PCK, it must contain data for this frame\.
+.
+.TP
+\fB\-k1\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels that should be used only for the first frame transformation to be computed\. Kernel names must be separated by spaces\.
+.
+.TP
+\fB\-f2\fR \fIframe\fR
+Specify the "from" frame for the second (or only) frame transformation to be computed\. This frame must be known to SPICE and can be specified using the frame name, ID, or class ID\.
+.
+.TP
+\fB\-t2\fR \fIframe\fR
+Specify the "to" frame for the second (or only) frame transformation to be computed\. This frame must be known to SPICE and can be specified using the name, ID, or class ID\.
+.
+.TP
+\fB\-c2\fR \fIframe\fR
+Specify the "coverage" frame to be used to look up the second coverage window\. This frame must be known to SPICE and must be either a PCK\-based (Class 2) or CK\-based (Class 3) frame\. It can be specified using the frame name, frame ID, or, if the second (or only) primary kernel is a CK or a binary PCK, class ID\. If the second (or only) primary kernel file is a CK or a binary PCK, it must contain data for this frame\.
+.
+.TP
+\fB\-k2\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels that should be used only for the second frame transformation to be computed\. Kernel names must be separated by spaces\.
+.
+.TP
+\fB\-b\fR \fItime\fR
+Specify the coverage window begin time\. This option must be provided when no primary kernels and "coverage" frames are specified\. The time string provided using this option can be in any form accepted by SPICE\.
+.
+.TP
+\fB\-e\fR \fItime\fR
+Specify the coverage window end time\. This option must be provided when no primary kernels and "coverage" frames are specified\. The time string provided using this option can be in any form accepted by SPICE\.
+.
+.TP
+\fB\-n\fR \fInumber\fR
+Specify the number of points within the coverage window, for which the frame transformation(s) must be computed\. The number must be an integer between 1 and 1,000,000\. The default value is 1000\.
+.
+.TP
+\fB\-s\fR \fIstep\fR
+Specify the step, in seconds, for determining points within the coverage window, for which the frame transformation(s) must be computed\. The step must be greater than 1E\-8\. This option supersedes \fB\-n\fR\.
+.
+.TP
+\fB\-t\fR \fIreport_type\fR
+Specify the type of report that the program should display\. By default, \fIreport_type\fR is \fBbasic\fR, which means it will display only the maximum rotation angle and angular velocity (AV) magnitude\.
+.
+.br
+If \fIreport_type\fR is \fBstats\fR, it will display statistics on rotation angles and AVs\.
+.
+.br
+If \fIreport_type\fR is \fBdumpaa\fR, it will display a table of rotation angles and axes\.
+.
+.br
+If \fIreport_type\fR is \fBdumpm\fR, it will display a table of matrices\.
+.
+.br
+If \fIreport_type\fR is \fBdumpqs\fR, it will display a table of SPICE\-style quaternions\.
+.
+.br
+If \fIreport_type\fR is \fBdumpqo\fR, it will display a table of "other"\-style quaternions\.
+.
+.br
+If \fIreport_type\fR is \fBdumpea\fR, it will display a table of Euler angles\.
+.
+.br
+If \fIreport_type\fR is \fBdumpc\fR, it will display a table of coverage intervals\.
+.
+.br
+If \fIreport_type\fR is \fBdumpg\fR, it will display a table of coverage gaps\.
+.
+.TP
+\fB\-a\fR \fIav_flag\fR
+Tell the program whether angular velocities should be computed along with rotations\. By default, \fIav_flag\fR is \fBno\fR, which means that only rotations are computed\. If \fIav_flag\fR is \fByes\fR, rotations and angular velocities are computed\.
+.
+.TP
+\fB\-m\fR \fIav_frame\fR
+Tell the program in which frame angular velocities should be reported\. By default, \fIav_frame\fR is \fBfrom\fR, which means it will output angular velocities in "from" frame\. If \fIav_frame\fR is \fBto\fR, it will output angular velocities in "to" frame\.
+.
+.TP
+\fB\-f\fR \fItime_type\fR
+Specify the type of time tag to be used in tabular reports\. By default, \fItime_type\fR is \fBet\fR, which means it will display times as TDB seconds past J2000\.
+.
+.br
+If \fItime_type\fR is \fBsclk\fR, it will display times as string SCLKs\.
+.
+.br
+If \fItime_type\fR is \fBsclkd\fR, it will display times as decimal SCLKs\.
+.
+.br
+If \fItime_type\fR is \fBticks\fR, it will display times as encoded SCLK ticks\.
+.
+.br
+\fItime_type\fR can also be any time format picture accepted by the TIMOUT routine (for example "YYYY\-MM\-DDTHR:MN:SC\.### ::RND" for time tags for be displayed as UTCs in ISO date format)
+.
+.TP
+\fB\-o\fR \fIaxes\fR
+Specify the list of axes determining the order of rotations used for converting rotation matrices to Euler angles\. The value must be a space\-delimited list of three axes from the set of "X", "Y", "Z" (case\-insensitive)\. The second axis must differ from the first and third axes\. The default order is "Z Y X"\.
+.
+.TP
+\fB\-x\fR \fIunit\fR
+Specify the units for the angles in the rotation angle and axis dump (\fB\-t dumpaa\fR) and Euler angle dump (\fB\-t dumpea\fR) reports; ignored for all other report types\. Supported units are: \fBradians\fR (by default), \fBdegrees\fR, \fBarcminutes\fR, \fBarcseconds\fR, \fBhourangle\fR, \fBminuteangle\fR and \fBsecondangle\fR\.
+.
+.TP
+\fB\-d\fR \fInumber\fR
+Specify the number of significant digits in the output numeric times (TDB seconds past J2000, decimal SCLKs and encoded SCLK ticks) and rotation component values or rotation difference component values included in the dump, coverage and coverage gap reports\. The number must be an integer between 6 and 17\. The default value is 14\.
+.
+.TP
+\fB\-v\fR
+Display only the version line\. This option overrides all other options\.
+.
+.TP
+\fB\-u\fR
+Display the usage message\. This option overrides all other options except \fB\-v\fR\.
+.
+.TP
+\fB\-h\fR
+Display a brief help message\. This option overrides all other options except \fB\-v\fR and \fB\-u\fR\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-frmdiff.md b/debian/man/cspice-frmdiff.md
new file mode 100644
index 0000000..92b65a7
--- /dev/null
+++ b/debian/man/cspice-frmdiff.md
@@ -0,0 +1,196 @@
+cspice-frmdiff(1) -- compute differences between two reference frames
+=====================================================================
+
+SYNOPSIS
+--------
+`cspice frmdiff` [_options_] _first_kernel_ _second_kernel_
+`cspice frmdiff` [_options_] _kernel_
+`cspice frmdiff` [_options_]
+
+
+DESCRIPTION
+-----------
+**FRMDIFF** provides means for sampling orientation of a single reference
+frame, or for comparing orientations of two reference frames known to SPICE
+and supported by data from SPICE kernels.
+
+To sample orientation of a single frame the program computes a set of
+transformations from one frame (the "from" frame) to another frame (the
+"to" frame) over an interval of time with fixed or variable time step,
+using a given set of kernel files. Then, depending on the requested type of
+output report, it prints to the screen a table containing these
+transformations expressed as total rotation angles and axes, quaternions,
+matrices or Euler angles and angular velocities, or only magnitude of the
+maximum rotation and angular velocity, or results of a simple statistical
+analysis of rotations.
+
+To compare orientations of two frames the program computes a set of
+transformations from one frame (the "from" frame) to another frame (the "to"
+frame) over an interval of time with a fixed or variable time step using one
+set of kernels, computes a set of transformations for the same or a
+different "from"-"to" frame combination at the same times using the same or
+a different set of kernels, and then computes the difference in rotation and
+angular velocity between the corresponding transformations. Depending on the
+requested type of output report the program prints to the screen only
+maximum differences in rotation and angular velocity, or a complete table of
+rotation and angular velocity differences expressed as total rotation angles
+and axes, matrices, quaternions, or Euler angles, or results of a simple
+statistical analysis of the rotation differences.
+
+**FRMDIFF** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+ * `-k` _kernel_ ...:
+ Specify the list of additional kernels that should be used for both
+ frame transformations to be computed. Kernel names must be separated by
+ spaces.
+
+ * `-f1` _frame_:
+ Specify the "from" frame for the first (or only) frame transformation to
+ be computed. This frame must be known to SPICE and can be specified
+ using the frame name, ID, or class ID.
+
+ * `-t1` _frame_:
+ Specify the "to" frame for the first (or only) frame transformation to
+ be computed. This frame must be known to SPICE and can be specified
+ using the frame name, ID, or class ID.
+
+ * `-c1` _frame_:
+ Specify the "coverage" frame to be used to look up the first coverage
+ window. This frame must be known to SPICE and must be either a PCK-based
+ (Class 2) or CK-based (Class 3) frame. It can be specified using the
+ frame name, frame ID, or, if the first (or only) primary kernel is a CK
+ or a binary PCK, class ID. If the first (or only) primary kernel file is
+ a CK or a binary PCK, it must contain data for this frame.
+
+ * `-k1` _kernel_ ...:
+ Specify the list of additional kernels that should be used only for the
+ first frame transformation to be computed. Kernel names must be
+ separated by spaces.
+
+ * `-f2` _frame_:
+ Specify the "from" frame for the second (or only) frame transformation
+ to be computed. This frame must be known to SPICE and can be specified
+ using the frame name, ID, or class ID.
+
+ * `-t2` _frame_:
+ Specify the "to" frame for the second (or only) frame transformation to
+ be computed. This frame must be known to SPICE and can be specified
+ using the name, ID, or class ID.
+
+ * `-c2` _frame_:
+ Specify the "coverage" frame to be used to look up the second coverage
+ window. This frame must be known to SPICE and must be either a PCK-based
+ (Class 2) or CK-based (Class 3) frame. It can be specified using the
+ frame name, frame ID, or, if the second (or only) primary kernel is a CK
+ or a binary PCK, class ID. If the second (or only) primary kernel file
+ is a CK or a binary PCK, it must contain data for this frame.
+
+ * `-k2` _kernel_ ...:
+ Specify the list of additional kernels that should be used only for the
+ second frame transformation to be computed. Kernel names must be
+ separated by spaces.
+
+ * `-b` _time_:
+ Specify the coverage window begin time. This option must be provided
+ when no primary kernels and "coverage" frames are specified. The time
+ string provided using this option can be in any form accepted by SPICE.
+
+ * `-e` _time_:
+ Specify the coverage window end time. This option must be provided when
+ no primary kernels and "coverage" frames are specified. The time string
+ provided using this option can be in any form accepted by SPICE.
+
+ * `-n` _number_:
+ Specify the number of points within the coverage window, for which the
+ frame transformation(s) must be computed. The number must be an integer
+ between 1 and 1,000,000. The default value is 1000.
+
+ * `-s` _step_:
+ Specify the step, in seconds, for determining points within the coverage
+ window, for which the frame transformation(s) must be computed. The step
+ must be greater than 1E-8. This option supersedes **-n**.
+
+ * `-t` _report_type_:
+ Specify the type of report that the program should display. By default,
+ _report_type_ is **basic**, which means it will display only the maximum
+ rotation angle and angular velocity (AV) magnitude.
+ If _report_type_ is **stats**, it will display statistics on rotation
+ angles and AVs.
+ If _report_type_ is **dumpaa**, it will display a table of rotation
+ angles and axes.
+ If _report_type_ is **dumpm**, it will display a table of matrices.
+ If _report_type_ is **dumpqs**, it will display a table of SPICE-style
+ quaternions.
+ If _report_type_ is **dumpqo**, it will display a table of "other"-style
+ quaternions.
+ If _report_type_ is **dumpea**, it will display a table of Euler angles.
+ If _report_type_ is **dumpc**, it will display a table of coverage
+ intervals.
+ If _report_type_ is **dumpg**, it will display a table of coverage gaps.
+
+ * `-a` _av_flag_:
+ Tell the program whether angular velocities should be computed along
+ with rotations. By default, _av_flag_ is **no**, which means that only
+ rotations are computed. If _av_flag_ is **yes**, rotations and angular
+ velocities are computed.
+
+ * `-m` _av_frame_:
+ Tell the program in which frame angular velocities should be reported.
+ By default, _av_frame_ is **from**, which means it will output angular
+ velocities in "from" frame. If _av_frame_ is **to**, it will output
+ angular velocities in "to" frame.
+
+ * `-f` _time_type_:
+ Specify the type of time tag to be used in tabular reports. By default,
+ _time_type_ is **et**, which means it will display times as TDB seconds
+ past J2000.
+ If _time_type_ is **sclk**, it will display times as string SCLKs.
+ If _time_type_ is **sclkd**, it will display times as decimal SCLKs.
+ If _time_type_ is **ticks**, it will display times as encoded SCLK ticks.
+ _time_type_ can also be any time format picture accepted by the TIMOUT
+ routine (for example "YYYY-MM-DDTHR:MN:SC.### ::RND" for time tags for
+ be displayed as UTCs in ISO date format)
+
+ * `-o` _axes_:
+ Specify the list of axes determining the order of rotations used for
+ converting rotation matrices to Euler angles. The value must be a
+ space-delimited list of three axes from the set of "X", "Y", "Z"
+ (case-insensitive). The second axis must differ from the first and third
+ axes. The default order is "Z Y X".
+
+ * `-x` _unit_:
+ Specify the units for the angles in the rotation angle and axis dump
+ (**-t dumpaa**) and Euler angle dump (**-t dumpea**) reports; ignored
+ for all other report types. Supported units are: **radians** (by
+ default), **degrees**, **arcminutes**, **arcseconds**, **hourangle**,
+ **minuteangle** and **secondangle**.
+
+ * `-d` _number_:
+ Specify the number of significant digits in the output numeric times
+ (TDB seconds past J2000, decimal SCLKs and encoded SCLK ticks) and
+ rotation component values or rotation difference component values
+ included in the dump, coverage and coverage gap reports. The number must
+ be an integer between 6 and 17. The default value is 14.
+
+ * `-v`:
+ Display only the version line. This option overrides all other options.
+
+ * `-u`:
+ Display the usage message. This option overrides all other options
+ except **-v**.
+
+ * `-h`:
+ Display a brief help message. This option overrides all other options
+ except **-v** and **-u**.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-inspekt.1 b/debian/man/cspice-inspekt.1
index bd6525c..c5e40f4 100644
--- a/debian/man/cspice-inspekt.1
+++ b/debian/man/cspice-inspekt.1
@@ -1,22 +1,22 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-INSPEKT 1
-.SH NAME
-cspice-inspekt \- interactively examine the contents of an E-Kernel
-
-.SH SYNOPSIS
-.B cspice-inspekt
-
-.SH DESCRIPTION
-.B cspice-inspekt
-is an interactive command-line program that examines the contents of an events component (ESQ) of an E-kernel. To access the built-in help please type "help;" (or "HELP;"), a menu will be displayed and at the prompt "Option: " type the number or letter shown in parentheses to the left of the topic of interest and hit RETURN. You will be presented with a screen of text that describes the topic.
-.PP
-.B cspice-inspekt
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-INSPEKT" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-inspekt\fR \- interactively examine the contents of an E\-Kernel
+.
+.SH "SYNOPSIS"
+\fBcspice inspekt\fR
+.
+.SH "DESCRIPTION"
+\fBINSPEKT\fR is an interactive command\-line program that examines the contents of an events component (ESQ) of an E\-kernel\. To access the built\-in help type "help;" (or "HELP;"), a menu will be displayed\. At the prompt "Option: " type the number or letter shown in parentheses to the left of the topic of interest and hit RETURN\. You will be presented with a screen of text that describes the topic\.
+.
+.P
+\fBINSPEKT\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-inspekt.md b/debian/man/cspice-inspekt.md
new file mode 100644
index 0000000..bba0355
--- /dev/null
+++ b/debian/man/cspice-inspekt.md
@@ -0,0 +1,27 @@
+cspice-inspekt(1) -- interactively examine the contents of an E-Kernel
+======================================================================
+
+SYNOPSIS
+--------
+`cspice inspekt`
+
+
+DESCRIPTION
+-----------
+**INSPEKT** is an interactive command-line program that examines the
+contents of an events component (ESQ) of an E-kernel. To access the built-in
+help type "help;" (or "HELP;"), a menu will be displayed. At the prompt
+"Option: " type the number or letter shown in parentheses to the left of the
+topic of interest and hit RETURN. You will be presented with a screen of
+text that describes the topic.
+
+**INSPEKT** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-mkdsk.1 b/debian/man/cspice-mkdsk.1
new file mode 100644
index 0000000..1e6029c
--- /dev/null
+++ b/debian/man/cspice-mkdsk.1
@@ -0,0 +1,79 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-MKDSK" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-mkdsk\fR \- creates a DSK file from a text file
+.
+.SH "SYNOPSIS"
+.
+.TP
+\fBcspice mkdsk\fR
+[\fB\-setup\fR \fIsetup_file\fR]
+.
+.br
+\fB\-input\fR \fIinput_data_file\fR
+.
+.br
+\fB\-output\fR \fIoutput_dsk_file\fR
+.
+.br
+[\fB\-h\fR|\fB\-t\fR|\fB\-u\fR|\fB\-v\fR]
+.
+.SH "DESCRIPTION"
+\fBMKDSK\fR converts a text file containing surface shape and size data to a binary Digital Shape Kernel (DSK)\.
+.
+.P
+The MKDSK program requires as input a setup file containing input parameters and a second file containing the shape data to be processed\.
+.
+.P
+Data files provided to this program either represent an object\'s surface as a collection of triangular plates, or as a height grid\.
+.
+.P
+Currently the only supported output DSK data type is type 2: this type represents the surface of a specified body as a collection of triangular plates\.
+.
+.P
+The program allows the user to optionally specify some descriptive text in a separate file, called the "comment file" to be placed into the "comment area" of the DSK file\. (Doing this is highly recommended\.)
+.
+.P
+For archival documentation purposes the content of the MKDSK setup file is automatically placed at the end of the "comment area" of the DSK file\.
+.
+.P
+\fBMKDSK\fR is part of the CSPICE Toolkit\. See cspice(7) for more information\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-setup\fR \fIsetup_file\fR
+If a setup file name isn\'t provided on the command line, MKDSK will prompt for it\. For more information on the setup file format please refer to the documentation\.
+.
+.TP
+\fB\-input\fR \fIinput_data_file\fR
+Specify the input shape data file\. If the input or output file names are provided on the command line, any corresponding file names assigned using setup keywords are ignored\.
+.
+.TP
+\fB\-output\fR \fIoutput_dsk_file\fR
+Specify the output DSK file\. If the input or output file names are provided on the command line, any corresponding file names assigned using setup keywords are ignored\.
+.
+.TP
+\fB\-h\fR, \fB\-help\fR
+Pint help message and exit\.
+.
+.TP
+\fB\-t\fR, \fB\-template\fR
+Print a complete MKDSK setup file template and exit\.
+.
+.TP
+\fB\-u\fR, \fB\-usage\fR
+Print usage information and exit\.
+.
+.TP
+\fB\-v\fR, \fB\-version\fR
+Print version and exit\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on http://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-mkdsk.md b/debian/man/cspice-mkdsk.md
new file mode 100644
index 0000000..2207792
--- /dev/null
+++ b/debian/man/cspice-mkdsk.md
@@ -0,0 +1,73 @@
+cspice-mkdsk(1) -- creates a DSK file from a text file
+=======================================================
+
+SYNOPSIS
+--------
+ * **cspice mkdsk**:
+ [**-setup** _setup_file_]
+ **-input** _input_data_file_
+ **-output** _output_dsk_file_
+ [**-h**|**-t**|**-u**|**-v**]
+
+
+DESCRIPTION
+-----------
+**MKDSK** converts a text file containing surface shape and size data
+to a binary Digital Shape Kernel (DSK).
+
+The MKDSK program requires as input a setup file containing input
+parameters and a second file containing the shape data to be processed.
+
+Data files provided to this program either represent an object's surface as a
+collection of triangular plates, or as a height grid.
+
+Currently the only supported output DSK data type is type 2: this type
+represents the surface of a specified body as a collection of triangular
+plates.
+
+The program allows the user to optionally specify some descriptive text in a
+separate file, called the "comment file" to be placed into the
+"comment area" of the DSK file. (Doing this is highly recommended.)
+
+For archival documentation purposes the content of the MKDSK setup file
+is automatically placed at the end of the "comment area" of the DSK file.
+
+**MKDSK** is part of the CSPICE Toolkit. See cspice(7) for more information.
+
+
+OPTIONS
+-------
+ * `-setup` _setup_file_:
+ If a setup file name isn't provided on the command line, MKDSK will
+ prompt for it. For more information on the setup file format please refer
+ to the documentation.
+
+ * `-input` _input_data_file_:
+ Specify the input shape data file. If the input or output file names are
+ provided on the command line, any corresponding file names assigned using
+ setup keywords are ignored.
+
+ * `-output` _output_dsk_file_:
+ Specify the output DSK file. If the input or output file names are
+ provided on the command line, any corresponding file names assigned using
+ setup keywords are ignored.
+
+ * `-h`, `-help`:
+ Pint help message and exit.
+
+ * `-t`, `-template`:
+ Print a complete MKDSK setup file template and exit.
+
+ * `-u`, `-usage`:
+ Print usage information and exit.
+
+ * `-v`, `-version`:
+ Print version and exit.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-mkspk.1 b/debian/man/cspice-mkspk.1
index f8ecc13..dc98d2c 100644
--- a/debian/man/cspice-mkspk.1
+++ b/debian/man/cspice-mkspk.1
@@ -1,57 +1,74 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-MKSPK 1
-.SH NAME
-cspice-mkspk \- creates an SPK file from trajectory information.
-
-.SH SYNOPSIS
-\fBcspice-mkspk\fR \fB\-setup\fR \fISETUP_FILE\fR [\fIOPTIONS\fR]
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-MKSPK" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-mkspk\fR \- creates an SPK file from trajectory information
+.
+.SH "SYNOPSIS"
+\fBcspice mkspk\fR \fB\-setup\fR \fIsetup_file\fR [\fIoptions\fR]
+.
.br
-\fBcspice-mkspk\fR \fB\-u\fR | \fB\-h\fR
+\fBcspice mkspk\fR \fB\-template\fR [\fIinput_type\fR \fIoutput_type\fR]
+.
.br
-\fBcspice-mkspk\fR \fB\-template\fR [\fIIMPUT_TYPE\fR \fIOUTPUT_TYPE\fR]
-
-.SH DESCRIPTION
-.B cspice-mkspk
-generates a new, or appends data to an existing, spacecraft or target body's ephemeris file in SPICE SPK format using one of the following SPK types: 5, 8, 9, 10, 12, 13, 15, 17. This SPK file is a binary file constructed according to the SPICE DAF (Double Precision Array File) architecture, containing one or more SPK data segments.
-.PP
-The program accepts one ASCII text file containing descriptions of input data (setup file) and a second ASCII text file (input file) containing the source ephemeris data to be processed.
-.PP
-Source ephemeris data can be time ordered lists of states (positions and velocities), sets of conic elements, sets of two-line elements, or a single set of equinoctial elements. All input data must be defined in a reference frame and relative to a body center both of which are specified in the setup file.
-.PP
-.B cspice-mkspk
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
+\fBcspice mkspk\fR \fB\-u\fR | \fB\-h\fR
+.
+.SH "DESCRIPTION"
+\fBMKSPK\fR is an utility program that generates a new, or appends data to an existing, spacecraft or target body\'s ephemeris file in SPICE SPK format using one of the following SPK types: 5, 8, 9, 10, 12, 13, 15, 17\. This SPK file is a binary file constructed according to the SPICE DAF (Double Precision Array File) architecture, containing one or more SPK data segments\.
+.
+.P
+The \fBMKSPK\fR program accepts one ASCII text file containing descriptions of input data (setup file) and a second ASCII text file (input file) containing the source ephemeris data to be processed\.
+.
+.P
+Source ephemeris data can be time ordered lists of states (positions and velocities), sets of conic elements, sets of two\-line elements, or a single set of equinoctial elements\. All input data must be defined in a reference frame and relative to a body center both of which are specified in the setup file\.
+.
+.P
+The program allows the user to optionally specify some descriptive text in a separate file (comment file) to be placed into the "comment area" of the SPK ephemeris file\. (Doing this is highly recommended\.)
+.
+.P
+For archival documentation purposes the content of the MKSPK setup file is automatically placed at the end of the "comment area" of the SPK file\.
+.
+.P
+\fBMKSPK\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+Command lines options can be provided in any order\. Option keys must be strictly lowercase\.
+.
.TP
-\fB\-setup\fR \fISETUP_FILE\fR
-Provide the setup file name. If input and output file names are provided, any file names assigned using setup file keywords are ignored.
+\fB\-setup\fR \fIsetup_file\fR
+Provide the setup file name\. If a setup file name isn\'t provided on the command line using the \fB\-setup\fR key, the program will prompt for it\. If options \fB\-input\fR or \fB\-output\fR are provided, any file names assigned using setup file keywords are ignored\.
+.
.TP
-\fB\-input\fR \fIIMPUT_FILE\fR
-Provide the input data file name. The input file must already exist.
+\fB\-input\fR \fIinput_file\fR
+Provide the input data file name\. The input file must already exist\.
+.
.TP
-\fB\-output\fR \fIOUTPUT_FILE\fR
-Provide the output SPK file name. The output must not exist unless the \fB\-append\fR option or the corresponding setup file keyword tells the program to run in the append mode.
+\fB\-output\fR \fIoutput_file\fR
+Provide the output SPK file name\. The output must not exist unless the \fB\-append\fR option or the corresponding setup file keyword tells the program to run in the append mode\.
+.
.TP
\fB\-append\fR
-Append new data to the specified output SPK file. If the SPK file specified after the \fB-output\fR option doesn't exist, then a new SPK file with the name specified will be created.
-.br
-Caution: if the program fails for any reason, it, in most cases, deletes the output file, even if it was appending data to an existing SPK file.
+Append new data to the specified output SPK file\. If the SPK file specified after the \fB\-output\fR option doesn\'t exist, then a new SPK file with the name specified will be created\.
+.
+.IP
+CAUTION: if the program fails for any reason, it, in most cases, deletes the output file, even if it was appending data to an existing SPK file\.
+.
.TP
\fB\-u\fR, \fB\-usage\fR
-Display usage information.
+Display usage information\.
+.
.TP
\fB\-h\fR, \fB\-help\fR
-Display a brief summary of the program's functionality.
+Display a brief summary of the program\'s functionality\.
+.
.TP
-\fB\-t\fR, \fB\-template\fR [\fIIMPUT_TYPE\fR \fIOUTPUT_TYPE\fR]
-Display either the complete setup file template or a type-specific setup file template and exit.
-If specified by itself, the program displays the complete setup file template including all required, optional, and conditional setup file keywords.
-To display a more concise, type-specific template, the \fIIMPUT_TYPE\fR (\fBstates\fR, \fBelements\fR, \fBeq_elements\fR, or \fBtl_elements\fR) and the \fIOUTPUT_TYPE\fR (\fB5\fR, \fB8\fR, \fB9\fR, \fB10\fR, \fB12\fR, \fB13\fR, \fB15\fR or \fB17\fR) can be specified. Such templates will include only keywords applicable for the specified type combination.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+\fB\-t\fR, \fB\-template\fR [\fIinput_type\fR \fIoutput_type\fR]
+Display either the complete setup file template or a type\-specific setup file template and exit\. If specified by itself, the program displays the complete setup file template including all required, optional, and conditional setup file keywords\. To display a more concise, type\-specific template, the \fIinput_type\fR (\fBstates\fR, \fBelements\fR, \fBeq_elements\fR, or \fBtl_elements\fR) and the \fIoutput_type\fR (\fB5\fR, \fB8\fR, \fB9\fR, \fB10\fR, \fB12\fR, \fB13\fR, \fB15\fR or \f [...]
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-mkspk.md b/debian/man/cspice-mkspk.md
new file mode 100644
index 0000000..0c85165
--- /dev/null
+++ b/debian/man/cspice-mkspk.md
@@ -0,0 +1,91 @@
+cspice-mkspk(1) -- creates an SPK file from trajectory information
+==================================================================
+
+SYNOPSIS
+--------
+`cspice mkspk` **-setup** _setup_file_ [_options_]
+`cspice mkspk` **-template** [_input_type_ _output_type_]
+`cspice mkspk` **-u** | **-h**
+
+
+DESCRIPTION
+-----------
+**MKSPK** is an utility program that generates a new, or appends data to an
+existing, spacecraft or target body's ephemeris file in SPICE SPK format
+using one of the following SPK types: 5, 8, 9, 10, 12, 13, 15, 17. This SPK
+file is a binary file constructed according to the SPICE DAF (Double
+Precision Array File) architecture, containing one or more SPK data segments.
+
+The **MKSPK** program accepts one ASCII text file containing descriptions of
+input data (setup file) and a second ASCII text file (input file) containing
+the source ephemeris data to be processed.
+
+Source ephemeris data can be time ordered lists of states (positions and
+velocities), sets of conic elements, sets of two-line elements, or a single
+set of equinoctial elements. All input data must be defined in a reference
+frame and relative to a body center both of which are specified in the setup
+file.
+
+The program allows the user to optionally specify some descriptive text in a
+separate file (comment file) to be placed into the "comment area" of the
+SPK ephemeris file. (Doing this is highly recommended.)
+
+For archival documentation purposes the content of the MKSPK setup file is
+automatically placed at the end of the "comment area" of the SPK file.
+
+**MKSPK** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+Command lines options can be provided in any order. Option keys must be
+strictly lowercase.
+
+ * `-setup` _setup_file_:
+ Provide the setup file name. If a setup file name isn't provided on the
+ command line using the **-setup** key, the program will prompt for it. If
+ options **-input** or **-output** are provided, any file names assigned
+ using setup file keywords are ignored.
+
+ * `-input` _input_file_:
+ Provide the input data file name. The input file must already exist.
+
+ * `-output` _output_file_:
+ Provide the output SPK file name. The output must not exist unless the
+ **-append** option or the corresponding setup file keyword tells the
+ program to run in the append mode.
+
+ * `-append`:
+ Append new data to the specified output SPK file. If the SPK file
+ specified after the **-output** option doesn't exist, then a new SPK
+ file with the name specified will be created.
+
+ CAUTION: if the program fails for any reason, it, in most cases, deletes
+ the output file, even if it was appending data to an existing SPK file.
+
+ * `-u`, `-usage`:
+ Display usage information.
+
+ * `-h`, `-help`:
+ Display a brief summary of the program's functionality.
+
+ * `-t`, `-template` [_input_type_ _output_type_]:
+ Display either the complete setup file template or a type-specific setup
+ file template and exit. If specified by itself, the program displays the
+ complete setup file template including all required, optional, and
+ conditional setup file keywords. To display a more concise,
+ type-specific template, the _input_type_ (**states**, **elements**,
+ **eq_elements**, or **tl_elements**) and the _output_type_ (**5**,
+ **8**, **9**, **10**, **12**, **13**, **15** or **17**) can be
+ specified. Such templates will include only keywords applicable for the
+ specified type combination.
+
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-msopck.1 b/debian/man/cspice-msopck.1
index f1b4513..98c754e 100644
--- a/debian/man/cspice-msopck.1
+++ b/debian/man/cspice-msopck.1
@@ -1,41 +1,54 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-MSOPCK 1
-.SH NAME
-cspice-msopck \- converts attitude data into a SPICE C-kernel.
-
-.SH SYNOPSIS
-\fBcspice-msopck\fR \fISETUP_FILE\fR \fIINPUT_DATA_FILE\fR \fIOUTPUT_CK_FILE\fR
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-MSOPCK" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-msopck\fR \- converts attitude data into a SPICE C\-kernel
+.
+.SH "SYNOPSIS"
+\fBcspice msopck\fR \fIsetup_file\fR \fIinput_data_file\fR \fIoutput_ck_file\fR
+.
.br
-\fBcspice-msopck\fR [\fIOPTIONS\fR]
-
-.SH DESCRIPTION
-.B cspice-msopck
-generates a new, or appends data to an existing, attitude data file in SPICE CK format using one of the following CK types: 1, 2, 3. This CK file is a binary file constructed according to the SPICE DAF (Double Precision Array File) architecture, containing one or more CK data segments.
-.PP
-The program accepts one ASCII text file containing descriptions of input data (setup file) and a second ASCII text file (input file) containing the source attitude data to be processed.
-.PP
-Source attitude data can be time ordered lists of quaternions, Euler angles, or matrices tagged with UTC, spacecraft on-board clock (SCLK), or Ephemeris Time (ET) times. All input data must provide attitude for a structure relative to a reference frame, both of which are specified in the setup file.
-.PP
-The program buffers the input data by chunks of 100,000 records and writes each chunk into a separate CK segment. It uses the same point as the end of the previous and the start of the next chunk to provide continuity at the segment boundary.
-.PP
-.B cspice-msopck
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
+\fBcspice msopck\fR [\fIoptions\fR]
+.
+.SH "DESCRIPTION"
+\fBMSOPCK\fR is a command\-line utility program that generates a new, or appends data to an existing, attitude data file in SPICE CK format using one of the following CK types: 1, 2, 3\. This CK file is a binary file constructed according to the SPICE DAF (Double Precision Array File) architecture, containing one or more CK data segments\.
+.
+.P
+The \fBMSOPCK\fR program accepts one ASCII text file containing descriptions of input data (setup file) and a second ASCII text file (input file) containing the source attitude data to be processed\.
+.
+.P
+Source attitude data can be time ordered lists of quaternions, Euler angles, or matrices tagged with UTC, spacecraft on\-board clock (SCLK), or Ephemeris Time (ET) times\. All input data must provide attitude for a structure relative to a reference frame, both of which are specified in the setup file\.
+.
+.P
+The program buffers the input data by chunks of 100,000 records and writes each chunk into a separate CK segment\. It uses the same point as the end of the previous and the start of the next chunk to provide continuity at the segment boundary\.
+.
+.P
+The program allows the user to optionally provide some descriptive text (metadata) in a separate file (comment file) to be placed into the "comment area" of the CK attitude file\. Doing this is highly recommended\.
+.
+.P
+For archival documentation purposes the content of the MSOPCK setup file is automatically placed into the "comment area" of the CK file\.
+.
+.P
+\fBMSOPCK\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+.
.TP
\fB\-u\fR, \fB\-usage\fR
-Display a brief usage message. This is the default behaviour if the command line has too few or too many arguments.
+Display a brief usage message\. This is the default behaviour if the command line has too few or too many arguments\.
+.
.TP
\fB\-h\fR, \fB\-help\fR
-Display a brief help message.
+Display a brief help message\.
+.
.TP
\fB\-t\fR, \fB\-template\fR
-Display the complete setup file template.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+Display the complete setup file template\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-msopck.md b/debian/man/cspice-msopck.md
new file mode 100644
index 0000000..597e072
--- /dev/null
+++ b/debian/man/cspice-msopck.md
@@ -0,0 +1,62 @@
+cspice-msopck(1) -- converts attitude data into a SPICE C-kernel
+================================================================
+
+SYNOPSIS
+--------
+`cspice msopck` _setup_file_ _input_data_file_ _output_ck_file_
+`cspice msopck` [_options_]
+
+
+DESCRIPTION
+-----------
+**MSOPCK** is a command-line utility program that generates a new, or appends
+data to an existing, attitude data file in SPICE CK format using one of the
+following CK types: 1, 2, 3. This CK file is a binary file constructed
+according to the SPICE DAF (Double Precision Array File) architecture,
+containing one or more CK data segments.
+
+The **MSOPCK** program accepts one ASCII text file containing descriptions of
+input data (setup file) and a second ASCII text file (input file) containing
+the source attitude data to be processed.
+
+Source attitude data can be time ordered lists of quaternions, Euler angles, or
+matrices tagged with UTC, spacecraft on-board clock (SCLK), or Ephemeris Time
+(ET) times. All input data must provide attitude for a structure relative to a
+reference frame, both of which are specified in the setup file.
+
+The program buffers the input data by chunks of 100,000 records and writes each
+chunk into a separate CK segment. It uses the same point as the end of the
+previous and the start of the next chunk to provide continuity at the segment
+boundary.
+
+The program allows the user to optionally provide some descriptive text
+(metadata) in a separate file (comment file) to be placed into the "comment
+area" of the CK attitude file. Doing this is highly recommended.
+
+For archival documentation purposes the content of the MSOPCK setup file is
+automatically placed into the "comment area" of the CK file.
+
+**MSOPCK** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+
+ * `-u`, `-usage`:
+ Display a brief usage message. This is the default behaviour if the
+ command line has too few or too many arguments.
+
+ * `-h`, `-help`:
+ Display a brief help message.
+
+ * `-t`, `-template`:
+ Display the complete setup file template.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-spacit.1 b/debian/man/cspice-spacit.1
index 7a09728..4dbd1dd 100644
--- a/debian/man/cspice-spacit.1
+++ b/debian/man/cspice-spacit.1
@@ -1,24 +1,28 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-SPACIT 1
-.SH NAME
-cspice-spacit \- manipulate and examine SPICE binary kernels
-
-.SH SYNOPSIS
-.B cspice-spacit
-
-.SH DESCRIPTION
-.B cspice-spacit
-is an interactive menu driven program which provides a collection of services useful for manipulating and examining SPICE binary kernel files. The program may be used to convert SPICE binary kernel files into equivalent ASCII files, called SPICE transfer files, and to convert the SPICE transfer files back to binary. SPACIT may also be used to summarize the information contained in SPICE binary kernel files and to read the comments contained in the comment area of a SPICE binary kernel file.
-.PP
-The program currently supports the CK, EK, PCK, and SPK SPICE binary kernel file formats.
-.PP
-.B cspice-spacit
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-SPACIT" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-spacit\fR \- manipulate and examine SPICE binary kernels
+.
+.SH "SYNOPSIS"
+\fBcspice spacit\fR
+.
+.SH "DESCRIPTION"
+\fBSPACIT\fR is an interactive menu driven program which provides a collection of services useful for manipulating and examining SPICE binary kernel files\. The program may be used to convert SPICE binary kernel files into equivalent ASCII files, called SPICE transfer files, and to convert the SPICE transfer files back to binary\. SPACIT may also be used to summarize the information contained in SPICE binary kernel files and to read the comments contained in the comment area of a SPICE b [...]
+.
+.P
+The \fBSPACIT\fR program currently supports the CK, EK, PCK, and SPK SPICE binary kernel file formats\.
+.
+.P
+In addition to SPICE binary kernel files, \fBSPACIT\fR requires additional SPICE files when used to summarize a binary kernel file\. A leap seconds kernel is required for summarizing CK, EK, PCK and SPK binary kernel files\. A SCLK kernel is required for summarizing binary CK files\.
+.
+.P
+\fBSPACIT\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-spacit.md b/debian/man/cspice-spacit.md
new file mode 100644
index 0000000..9054922
--- /dev/null
+++ b/debian/man/cspice-spacit.md
@@ -0,0 +1,36 @@
+cspice-spacit(1) -- manipulate and examine SPICE binary kernels
+===============================================================
+
+SYNOPSIS
+--------
+`cspice spacit`
+
+
+DESCRIPTION
+-----------
+**SPACIT** is an interactive menu driven program which provides a collection
+of services useful for manipulating and examining SPICE binary kernel files.
+The program may be used to convert SPICE binary kernel files into equivalent
+ASCII files, called SPICE transfer files, and to convert the SPICE transfer
+files back to binary. SPACIT may also be used to summarize the information
+contained in SPICE binary kernel files and to read the comments contained in
+the comment area of a SPICE binary kernel file.
+
+The **SPACIT** program currently supports the CK, EK, PCK, and SPK SPICE binary
+kernel file formats.
+
+In addition to SPICE binary kernel files, **SPACIT** requires additional
+SPICE files when used to summarize a binary kernel file. A leap seconds
+kernel is required for summarizing CK, EK, PCK and SPK binary kernel files.
+A SCLK kernel is required for summarizing binary CK files.
+
+**SPACIT** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-spkdiff.1 b/debian/man/cspice-spkdiff.1
index 44326ff..b8354d8 100644
--- a/debian/man/cspice-spkdiff.1
+++ b/debian/man/cspice-spkdiff.1
@@ -1,99 +1,128 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-SPKDIFF 1
-.SH NAME
-cspice-spkdiff \- compare or sample trajectories of two bodies
-
-.SH SYNOPSIS
-\fBcspice-spkdiff\fR [\fIOPTIONS\fR] \fIFIRST_SPK\fR \fISECOND_SPK\fR
-\fBcspice-spkdiff\fR [\fIOPTIONS\fR] \fISPK_FILE\fR
-\fBcspice-spkdiff\fR [\fIOPTIONS\fR]
-
-.SH DESCRIPTION
-.B cspice-spkdiff
-provides means for comparing the trajectories of two bodies or sampling the trajectory of a single body known to SPICE and supported by data from SPICE kernels.
-.PP
-To compare trajectories the program computes a set of geometric states of a body as seen from a center in a reference frame over an interval of time with a fixed or variable time step using one SPK file, computes a set of geometric states for the same or different body-center-frame combination at the same times using the other SPK file, and then subtracts the corresponding states from each other. Depending on the type of output report requested the program prints to the screen only the m [...]
-.PP
-To sample trajectory of a body the program computes a set of geometric states of a body as seen from a center in a reference frame over an interval of time with fixed or variable time step, using a given set of kernel files, and prints to the screen a table containing these states.
-.PP
-.B cspice-spkdiff
-is part of the SPICE Toolkit. See \fBcspice\fR(7).
-
-.SH OPTIONS
-.TP
-\fB\-k\fR \fIKERNEL\fR ...
-Specify the list of additional kernels or meta-kernels that are needed for both trajectories to be computed.
-.TP
-\fB\-b1\fR \fIBODY\fR
-Specify the body for the first trajectory to be computed. This body can be specified using its NAIF ID or name. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options.
-.TP
-\fB\-c1\fR \fIBODY\fR
-Specify the center for the first trajectory to be computed. This center can be specified using its NAIF ID or name. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options.
-.TP
-\fB\-r1\fR \fIFRAME\fR
-Specify the name of the reference frame for the first trajectory to be computed. The frame can be any of the frames built into SPICE or frames defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options.
-.TP
-\fB\-k1\fR \fIKERNEL\fR ...
-Specify the list of additional kernels or meta-kernels that are needed only for the first trajectory to be computed.
-.TP
-\fB\-b2\fR \fIBODY\fR
-Specify the body for the second trajectory to be computed. This body can be specified using its NAIF ID or name. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options.
-.TP
-\fB\-c2\fR \fIBODY\fR
-Specify the center for the second trajectory to be computed. This center can be specified using its NAIF ID or name. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options.
-.TP
-\fB\-r2\fR \fIFRAME\fR
-Specify the name of the reference frame for the second trajectory to be computed. The frame can be any of the frames built into SPICE or frames defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options.
-.TP
-\fB\-k2\fR \fIKERNEL\fR ...
-Specify the list of additional kernels or meta-kernels that are needed only for the second trajectory to be computed.
-.TP
-\fB\-b\fR \fITIME\fR
-Specify the coverage window begin time. The time string provided using this option can be in any form accepted by SPICE. If this option is provided, the name of an LSK file must be provided with the \fB\-k\fR, \fB\-k1\fR, or \fB\-k2\fR option.
-.TP
-\fB\-e\fR \fITIME\fR
-Specify the coverage window end time. The time string provided using this option can be in any form accepted by SPICE. If this option is provided, the name of an LSK file must be provided with the \fB\-k\fR, \fB\-k1\fR, or \fB\-k2\fR option.
-.TP
-\fB\-s\fR \fISTEP\fR
-Specify the step, in TDB seconds, for determining points within the coverage window, for which the trajectory(ies) are to be computed. The step must be greater than 1E-8. This option supersedes \fB\-n\fR.
-.TP
-\fB\-n\fR \fINUMBER\fR
-Specify the number of points within the coverage window, for which the trajectory(ies) are to be computed. The number must be an integer between 2 and 1,000,000. The default value is 1000.
-.TP
-\fB\-f\fR \fITIME_TYPE\fR ...
-Specify the output time format other than the default TDB seconds past J2000. The value can be any time format picture accepted by SPICE. For example to display time tags as UTCs in ISO date format use 'YYYY-MM-DDTHR:MN:SC.### ::RND', to display time tags as TDB Julian days use 'JULIAND.######### ::TDB'.
-.TP
-\fB\-d\fR \fINUMBER\fR
-Specify the number of significant digits in the output numeric times (TDB seconds past J2000) and state component values or state component difference values included in the dump, coverage and coverage gap reports. The number must be an integer between 6 and 17. The default value is 14.
-.TP
-\fB\-t\fR \fIREPORT_TYPE\fR
-Specify the type of report that the program should display.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-SPKDIFF" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-spkdiff\fR \- compare or sample trajectories of two bodies
+.
+.SH "SYNOPSIS"
+\fBcspice spkdiff\fR [\fIoptions\fR] \fIfirst_spk\fR \fIsecond_spk\fR
+.
.br
-If \fIREPORT_TYPE\fR is \fBbasic\fR, it will display only the absolute and relative maximum and average differences in magnitude of position and velocity vectors. This is the default type for comparison runs.
+\fBcspice spkdiff\fR [\fIoptions\fR] \fIfirst_spk\fR
+.
.br
-If \fIREPORT_TYPE\fR is \fBstats\fR, it will display statistics on position differences rotated into the view frame.
+\fBcspice spkdiff\fR \fB\-v\fR | \fB\-u\fR | \fB\-h\fR
+.
+.SH "DESCRIPTION"
+\fBSPKDIFF\fR provides means for comparing the trajectories of two bodies or sampling the trajectory of a single body known to SPICE and supported by data from SPICE kernels\.
+.
+.P
+To compare trajectories the program computes a set of geometric states of a body as seen from a center in a reference frame over an interval of time with a fixed or variable time step using one SPK file, computes a set of geometric states for the same or different body\-center\-frame combination at the same times using the other SPK file, and then subtracts the corresponding states from each other\. Depending on the type of output report requested the program prints to the screen only th [...]
+.
+.P
+To sample trajectory of a body the program computes a set of geometric states of a body as seen from a center in a reference frame over an interval of time with fixed or variable time step, using a given set of kernel files, and prints to the screen a table containing these states\.
+.
+.P
+\fBSPKDIFF\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+The order of options and case of the option keys are not significant\. The values provided after the option keys must be separated from the keys by one or more spaces\. Unrecognized options are not specifically checked for; instead they are treated as continuation of the value provided using the preceding recognized option\.
+.
+.TP
+\fB\-k\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels or meta\-kernels that are needed for both trajectories to be computed\. File names following \fB\-k\fR must be separated by spaces\.
+.
+.TP
+\fB\-b1\fR \fIbody\fR
+Specify the body for the first trajectory to be computed\. This body can be specified using its NAIF ID or name\. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options\.
+.
+.TP
+\fB\-c1\fR \fIbody\fR
+Specify the center for the first trajectory to be computed\. This center can be specified using its NAIF ID or name\. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options\.
+.
+.TP
+\fB\-r1\fR \fIframe\fR
+Specify the name of the reference frame for the first trajectory to be computed\. The frame can be any of the frames built into SPICE or frames defined by kernels provided using the \fB\-k\fR and \fB\-k1\fR options\.
+.
+.TP
+\fB\-k1\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels or meta\-kernels that are needed only for the first trajectory to be computed\.
+.
+.TP
+\fB\-b2\fR \fIbody\fR
+Specify the body for the second trajectory to be computed\. This body can be specified using its NAIF ID or name\. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options\.
+.
+.TP
+\fB\-c2\fR \fIbody\fR
+Specify the center for the second trajectory to be computed\. This center can be specified using its NAIF ID or name\. If the name is used, it must be either built into SPICE or defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options\.
+.
+.TP
+\fB\-r2\fR \fIframe\fR
+Specify the name of the reference frame for the second trajectory to be computed\. The frame can be any of the frames built into SPICE or frames defined by kernels provided using the \fB\-k\fR and \fB\-k2\fR options\.
+.
+.TP
+\fB\-k2\fR \fIkernel\fR \.\.\.
+Specify the list of additional kernels or meta\-kernels that are needed only for the second trajectory to be computed\.
+.
+.TP
+\fB\-b\fR \fItime\fR
+Specify the coverage window begin time\. The time string provided using this option can be in any form accepted by SPICE\. If this option is provided, the name of an LSK file must be provided with the \fB\-k\fR, \fB\-k1\fR, or \fB\-k2\fR option\.
+.
+.TP
+\fB\-e\fR \fItime\fR
+Specify the coverage window end time\. The time string provided using this option can be in any form accepted by SPICE\. If this option is provided, the name of an LSK file must be provided with the \fB\-k\fR, \fB\-k1\fR, or \fB\-k2\fR option\.
+.
+.TP
+\fB\-s\fR \fIstep\fR
+Specify the step, in TDB seconds, for determining points within the coverage window, for which the trajectory(ies) are to be computed\. The step must be greater than 1E\-8\. This option supersedes \fB\-n\fR\.
+.
+.TP
+\fB\-n\fR \fInumber\fR
+Specify the number of points within the coverage window, for which the trajectory(ies) are to be computed\. The number must be an integer between 2 and 1,000,000\. The default value is 1000\.
+.
+.TP
+\fB\-f\fR \fItime_type\fR \.\.\.
+Specify the output time format other than the default TDB seconds past J2000\. The value can be any time format picture accepted by SPICE\. For example to display time tags as UTCs in ISO date format use \'YYYY\-MM\-DDTHR:MN:SC\.### ::RND\', to display time tags as TDB Julian days use \'JULIAND\.######### ::TDB\'\.
+.
+.TP
+\fB\-d\fR \fInumber\fR
+Specify the number of significant digits in the output numeric times (TDB seconds past J2000) and state component values or state component difference values included in the dump, coverage and coverage gap reports\. The number must be an integer between 6 and 17\. The default value is 14\.
+.
+.TP
+\fB\-t\fR \fIreport_type\fR
+Specify the type of report that the program should display\. If \fIreport_type\fR is \fBbasic\fR, it will display only the absolute and relative maximum and average differences in magnitude of position and velocity vectors\. This is the default type for comparison runs\.
+.
.br
-If \fIREPORT_TYPE\fR is \fBdump\fR, it will display a table of positions and velocities or their differences. This is the default type for sampling runs.
+If \fIreport_type\fR is \fBstats\fR, it will display statistics on position differences rotated into the view frame\.
+.
.br
-If \fIREPORT_TYPE\fR is \fBdumpvf\fR, it will display a table of position and velocity differences rotated into the view frame.
+If \fIreport_type\fR is \fBdump\fR, it will display a table of positions and velocities or their differences\. This is the default type for sampling runs\.
+.
.br
-If \fIREPORT_TYPE\fR is \fBdumpc\fR, it will display a table of coverage intervals.
+If \fIreport_type\fR is \fBdumpvf\fR, it will display a table of position and velocity differences rotated into the view frame\.
+.
.br
-If \fIREPORT_TYPE\fR is \fBdumpg\fR, it will display a table of gaps in coverage.
+If \fIreport_type\fR is \fBdumpc\fR, it will display a table of coverage intervals\.
+.
+.br
+If \fIreport_type\fR is \fBdumpg\fR, it will display a table of gaps in coverage\.
+.
.TP
\fB\-v\fR
-Display only the version line. This option overrides all other options.
+Display only the version line\. This option overrides all other options\.
+.
.TP
\fB\-u\fR
-Display the usage message. This option overrides all other options except \fB\-v\fR.
+Display the usage message\. This option overrides all other options except \fB\-v\fR\.
+.
.TP
\fB\-h\fR
-Display a brief help message. This option overrides all other options except \fB\-v\fR and \fB\-u\fR.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+Display a brief help message\. This option overrides all other options except \fB\-v\fR and \fB\-u\fR\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-spkdiff.md b/debian/man/cspice-spkdiff.md
new file mode 100644
index 0000000..9be28b8
--- /dev/null
+++ b/debian/man/cspice-spkdiff.md
@@ -0,0 +1,163 @@
+cspice-spkdiff(1) -- compare or sample trajectories of two bodies
+=================================================================
+
+SYNOPSIS
+--------
+`cspice spkdiff` [_options_] _first_spk_ _second_spk_
+`cspice spkdiff` [_options_] _first_spk_
+`cspice spkdiff` **-v** | **-u** | **-h**
+
+
+DESCRIPTION
+-----------
+**SPKDIFF** provides means for comparing the trajectories of two bodies or
+sampling the trajectory of a single body known to SPICE and supported by
+data from SPICE kernels.
+
+To compare trajectories the program computes a set of geometric states of a
+body as seen from a center in a reference frame over an interval of time
+with a fixed or variable time step using one SPK file, computes a set of
+geometric states for the same or different body-center-frame combination at
+the same times using the other SPK file, and then subtracts the
+corresponding states from each other. Depending on the type of output report
+requested the program prints to the screen only the maximum differences in
+position and velocity, or a complete table of position and velocity
+differences, or a complete table of differences expressed in "view frame"
+coordinates, or results of a simple statistical analysis of the differences
+expressed in "view frame" coordinates.
+
+To sample trajectory of a body the program computes a set of geometric
+states of a body as seen from a center in a reference frame over an interval
+of time with fixed or variable time step, using a given set of kernel files,
+and prints to the screen a table containing these states.
+
+**SPKDIFF** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+The order of options and case of the option keys are not significant. The
+values provided after the option keys must be separated from the keys by one
+or more spaces. Unrecognized options are not specifically checked for;
+instead they are treated as continuation of the value provided using the
+preceding recognized option.
+
+ * `-k` _kernel_ ...:
+ Specify the list of additional kernels or meta-kernels that are needed
+ for both trajectories to be computed. File names following **-k** must
+ be separated by spaces.
+
+ * `-b1` _body_:
+ Specify the body for the first trajectory to be computed. This body can
+ be specified using its NAIF ID or name. If the name is used, it must be
+ either built into SPICE or defined by kernels provided using the **-k**
+ and **-k1** options.
+
+ * `-c1` _body_:
+ Specify the center for the first trajectory to be computed. This center
+ can be specified using its NAIF ID or name. If the name is used, it must
+ be either built into SPICE or defined by kernels provided using the
+ **-k** and **-k1** options.
+
+ * `-r1` _frame_:
+ Specify the name of the reference frame for the first trajectory to be
+ computed. The frame can be any of the frames built into SPICE or frames
+ defined by kernels provided using the **-k** and **-k1** options.
+
+ * `-k1` _kernel_ ...:
+ Specify the list of additional kernels or meta-kernels that are needed
+ only for the first trajectory to be computed.
+
+ * `-b2` _body_:
+ Specify the body for the second trajectory to be computed. This body can
+ be specified using its NAIF ID or name. If the name is used, it must be
+ either built into SPICE or defined by kernels provided using the **-k**
+ and **-k2** options.
+
+ * `-c2` _body_:
+ Specify the center for the second trajectory to be computed. This center
+ can be specified using its NAIF ID or name. If the name is used, it must
+ be either built into SPICE or defined by kernels provided using the
+ **-k** and **-k2** options.
+
+ * `-r2` _frame_:
+ Specify the name of the reference frame for the second trajectory to be
+ computed. The frame can be any of the frames built into SPICE or frames
+ defined by kernels provided using the **-k** and **-k2** options.
+
+ * `-k2` _kernel_ ...:
+ Specify the list of additional kernels or meta-kernels that are needed
+ only for the second trajectory to be computed.
+
+ * `-b` _time_:
+ Specify the coverage window begin time. The time string provided using
+ this option can be in any form accepted by SPICE. If this option is
+ provided, the name of an LSK file must be provided with the **-k**,
+ **-k1**, or **-k2** option.
+
+ * `-e` _time_:
+ Specify the coverage window end time. The time string provided using
+ this option can be in any form accepted by SPICE. If this option is
+ provided, the name of an LSK file must be provided with the **-k**,
+ **-k1**, or **-k2** option.
+
+ * `-s` _step_:
+ Specify the step, in TDB seconds, for determining points within the
+ coverage window, for which the trajectory(ies) are to be computed. The
+ step must be greater than 1E-8. This option supersedes **-n**.
+
+ * `-n` _number_:
+ Specify the number of points within the coverage window, for which the
+ trajectory(ies) are to be computed. The number must be an integer
+ between 2 and 1,000,000. The default value is 1000.
+
+ * `-f` _time_type_ ...:
+ Specify the output time format other than the default TDB seconds past
+ J2000. The value can be any time format picture accepted by SPICE. For
+ example to display time tags as UTCs in ISO date format use
+ 'YYYY-MM-DDTHR:MN:SC.### ::RND', to display time tags as TDB Julian days
+ use 'JULIAND.######### ::TDB'.
+
+ * `-d` _number_:
+ Specify the number of significant digits in the output numeric times
+ (TDB seconds past J2000) and state component values or state component
+ difference values included in the dump, coverage and coverage gap
+ reports. The number must be an integer between 6 and 17. The default
+ value is 14.
+
+ * `-t` _report_type_:
+ Specify the type of report that the program should display. If
+ _report_type_ is **basic**, it will display only the absolute and
+ relative maximum and average differences in magnitude of position and
+ velocity vectors. This is the default type for comparison runs.
+ If _report_type_ is **stats**, it will display statistics on position
+ differences rotated into the view frame.
+ If _report_type_ is **dump**, it will display a table of positions and
+ velocities or their differences. This is the default type for sampling
+ runs.
+ If _report_type_ is **dumpvf**, it will display a table of position and
+ velocity differences rotated into the view frame.
+ If _report_type_ is **dumpc**, it will display a table of coverage
+ intervals.
+ If _report_type_ is **dumpg**, it will display a table of gaps in
+ coverage.
+
+ * `-v`:
+ Display only the version line. This option overrides all other options.
+
+ * `-u`:
+ Display the usage message. This option overrides all other options
+ except **-v**.
+
+ * `-h`:
+ Display a brief help message. This option overrides all other options
+ except **-v** and **-u**.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-spkmerge.1 b/debian/man/cspice-spkmerge.1
index f394a6c..d0e3ecc 100644
--- a/debian/man/cspice-spkmerge.1
+++ b/debian/man/cspice-spkmerge.1
@@ -1,26 +1,28 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-SPKMERGE 1
-.SH NAME
-cspice-spkmerge \- subset or merge one or more SPICE SPK files
-
-.SH SYNOPSIS
-\fBcspice-spkmerge\fR \fICOMMAND_FILE\fR
-
-.SH DESCRIPTION
-.B cspice-spkmerge
-builds new SPK files by merging entire or subsets of one or more existing SPK files. It creates SPK kernels that have no overlapping ephemeris; the order in which source files are specified determines the precedence when source files contain overlapping data.
-.PP
-.B cspice-spkmerge
-reads all its instructions from a command file. A command file is an ASCII formatted file containing 'KEYWORD = value' assignments.
-.PP
-.B cspice-spkmerge
-is part of the SPICE Toolkit. See
-.BR cspice (7).
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-SPKMERGE" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-spkmerge\fR \- subset or merge one or more SPICE SPK files
+.
+.SH "SYNOPSIS"
+\fBcspice spkmerge\fR [\fIcommand_file\fR]
+.
+.SH "DESCRIPTION"
+\fBSPKMERGE\fR builds new SPK files by merging entire or subsets of one or more existing SPK files\. \fBSPKMERGE\fR creates SPK kernels that have no overlapping ephemeris; the order in which source files are specified determines the precedence when source files contain overlapping data\.
+.
+.P
+\fBSPKMERGE\fR reads all its instructions from a command file\. A command file is an ASCII formatted file containing `KEYWORD = value\' assignments\. The format of this file is thoroughly described in the documentation file spkmerge\.ug\.
+.
+.P
+\fBSPKMERGE\fR will prompt for the name of the command file when you start the program\. Alternately, you can name the command file as the only argument on the command line\.
+.
+.P
+\fBSPKMERGE\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-spkmerge.md b/debian/man/cspice-spkmerge.md
new file mode 100644
index 0000000..d18893a
--- /dev/null
+++ b/debian/man/cspice-spkmerge.md
@@ -0,0 +1,34 @@
+cspice-spkmerge(1) -- subset or merge one or more SPICE SPK files
+=================================================================
+
+SYNOPSIS
+--------
+`cspice spkmerge` [_command_file_]
+
+
+DESCRIPTION
+-----------
+**SPKMERGE** builds new SPK files by merging entire or subsets of one or
+more existing SPK files. **SPKMERGE** creates SPK kernels that have no
+overlapping ephemeris; the order in which source files are specified
+determines the precedence when source files contain overlapping data.
+
+**SPKMERGE** reads all its instructions from a command file. A command file
+is an ASCII formatted file containing `KEYWORD = value' assignments. The
+format of this file is thoroughly described in the documentation file
+spkmerge.ug.
+
+**SPKMERGE** will prompt for the name of the command file when you start the
+program. Alternately, you can name the command file as the only argument on
+the command line.
+
+**SPKMERGE** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-tobin.1 b/debian/man/cspice-tobin.1
index c13f455..7aedcc2 100644
--- a/debian/man/cspice-tobin.1
+++ b/debian/man/cspice-tobin.1
@@ -1,25 +1,28 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-TOBIN 1
-.SH NAME
-cspice-tobin \- converts transfer format SPICE files to binary format
-
-.SH SYNOPSIS
-\fBcspice-tobin\fR \fITRANSFER_FORMAT_FILE\fR [\fIBINARY_FORMAT_FILE\fR]
-
-.SH DESCRIPTION
-.B cspice-tobin
-is a command-line program that converts transfer format SPK, CK and EK files into it's binary format for use in a particular computing environment. It requires at least the name of the input transfer file, which is the first argument on the command line. Optionally, a name for the output binary file may be specified as the second argument on the command line. If a name for the output file is provided it overrides the automatic naming conventions used by the program.
-.PP
-If only the name of the input transfer file is provided on the command line, the program will generate a name for the output binary kernel file that has the same base name as the input transfer file and an appropriate filename extension, based on the filename extension of the transfer file. If it does not recognize the filename extension of the input transfer file, or there is no filename extension on the input transfer file, a filename extension of '.bin' will be used as the filename ex [...]
-.PP
-.B cspice-tobin
-is part of the SPICE Toolkit. See
-.BR cspice (7).
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-TOBIN" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-tobin\fR \- converts transfer format SPICE files to binary format
+.
+.SH "SYNOPSIS"
+\fBcspice tobin\fR \fItransfer_format_file\fR [\fIbinary_format_file\fR]
+.
+.SH "DESCRIPTION"
+\fBTOBIN\fR converts a SPICE transfer format SPK, CK, PCK, DSK and EK file into it\'s binary format for use in a particular computing environment\. \fBTOBIN\fR requires at least the name of the input transfer file, which is the first argument on the command line\. Optionally, a name for the output binary file may be specified as the second argument on the command line\. If a name for the output file is provided it overrides the automatic naming conventions used by the program\.
+.
+.P
+If only the name of the input transfer file is provided on the command line, TOBIN will generate a name for the output binary kernel file that has the same base name as the input transfer file and an appropriate filename extension, based on the filename extension of the transfer file\. If \fBTOBIN\fR does not recognize the filename extension of the input transfer file, or there is no filename extension on the input transfer file, a filename extension of \'\.bin\' will be used as the file [...]
+.
+.P
+\fBTOBIN\fR recognizes the transfer filename extensions "\.xc", "\.xee", "\.xpc", and "\.xsp" associated with transfer files for SPICE data products\. These are converted to the SPICE binary kernel filename extensions "\.bc", "\.bee", "\.bpc", and "\.bsp," respectively\. Also recognized are the old transfer file extensions "\.tc", "\.tee", "\.tpc", and "\.tsp," which are converted into the appropriate filename extensions for a binary kernel file\.
+.
+.P
+\fBTOBIN\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-tobin.md b/debian/man/cspice-tobin.md
new file mode 100644
index 0000000..db6ece9
--- /dev/null
+++ b/debian/man/cspice-tobin.md
@@ -0,0 +1,46 @@
+cspice-tobin(1) -- converts transfer format SPICE files to binary format
+========================================================================
+
+SYNOPSIS
+--------
+`cspice tobin` _transfer_format_file_ [_binary_format_file_]
+
+
+DESCRIPTION
+-----------
+**TOBIN** converts a SPICE transfer format SPK, CK, PCK, DSK and EK file
+into it's binary format for use in a particular computing environment.
+**TOBIN** requires at least the name of the input transfer file, which is
+the first argument on the command line. Optionally, a name for the output
+binary file may be specified as the second argument on the command line. If
+a name for the output file is provided it overrides the automatic naming
+conventions used by the program.
+
+If only the name of the input transfer file is provided on the command line,
+TOBIN will generate a name for the output binary kernel file that has the
+same base name as the input transfer file and an appropriate filename
+extension, based on the filename extension of the transfer file. If
+**TOBIN** does not recognize the filename extension of the input transfer
+file, or there is no filename extension on the input transfer file, a
+filename extension of '.bin' will be used as the filename extension of the
+output binary file. If a file having the same name as the output file
+already exists, **TOBIN** signals an error and stops. We assume that it is
+bad form to overwrite or replace an existing file.
+
+**TOBIN** recognizes the transfer filename extensions ".xc", ".xee", ".xpc",
+and ".xsp" associated with transfer files for SPICE data products. These are
+converted to the SPICE binary kernel filename extensions ".bc", ".bee",
+".bpc", and ".bsp," respectively. Also recognized are the old transfer file
+extensions ".tc", ".tee", ".tpc", and ".tsp," which are converted into the
+appropriate filename extensions for a binary kernel file.
+
+**TOBIN** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-toxfr.1 b/debian/man/cspice-toxfr.1
index 001e9ce..94dcf54 100644
--- a/debian/man/cspice-toxfr.1
+++ b/debian/man/cspice-toxfr.1
@@ -1,25 +1,28 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-TOXFR 1
-.SH NAME
-cspice-toxfr \- converts binary format SPICE files to transfer format
-
-.SH SYNOPSIS
-\fBcspice-toxfr\fR \fIBINARY_FORMAT_FILE\fR [\fITRANSFER_FORMAT_FILE\fR]
-
-.SH DESCRIPTION
-.B cspice-toxfr
-is a command-line program that converts binary format SPK, CK and EK files into a transfer file format that is used to transfer, or port, the binary data to a different computing environment. It requires at least the name of the input binary file, which is the first argument on the command line. Optionally, a name for the output transfer file may be specified as the second argument on the command line. If a name for the output file is provided on the command line it overrides the automat [...]
-.PP
-If only the name of the input binary file is provided on the command line, the program will generate a name for the output transfer file that has the same base name as the input binary file and an appropriate filename extension, based on the filename extension of the binary file. If it does not recognize the filename extension of the input binary file, or there is no filename extension on the input binary file, a filename extension of '.xfr' will be used as the filename extension of the [...]
-.PP
-.B cspice-toxfr
-is part of the SPICE Toolkit. See
-.BR cspice (7).
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-TOXFR" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-toxfr\fR \- converts binary format SPICE files to transfer format
+.
+.SH "SYNOPSIS"
+\fBcspice toxfr\fR \fItransfer_format_file\fR [\fIbinary_format_file\fR]
+.
+.SH "DESCRIPTION"
+\fBTOXFR\fR converts a SPICE binary format SPK, CK, PCK, DSK and EK file into a transfer file format that is used to transfer, or port, the binary data to a different computing environment\. \fBTOXFR\fR requires at least the name of the input binary file, which is the first argument on the command line\. Optionally, a name for the output transfer file may be specified as the second argument on the command line\. If a name for the output file is provided on the command line it overrides t [...]
+.
+.P
+If only the name of the input binary file is provided on the command line, \fBTOXFR\fR will generate a name for the output transfer file that has the same base name as the input binary file and an appropriate filename extension, based on the filename extension of the binary file\. If \fBTOXFR\fR does not recognize the filename extension of the input binary file, or there is no filename extension on the input binary file, a filename extension of \'\.xfr\' will be used as the filename exte [...]
+.
+.P
+\fBTOXFR\fR recognizes the filename extensions "\.bc", "\.bee", "\.bpc", and "\.bsp" which are associated with SPICE binary kernel files\. These are converted to the transfer filename extensions "\.xc", "\.xee", "\.xpc", and "\.xsp," respectively\.
+.
+.P
+\fBTOXFR\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-toxfr.md b/debian/man/cspice-toxfr.md
new file mode 100644
index 0000000..be4b567
--- /dev/null
+++ b/debian/man/cspice-toxfr.md
@@ -0,0 +1,45 @@
+cspice-toxfr(1) -- converts binary format SPICE files to transfer format
+========================================================================
+
+SYNOPSIS
+--------
+`cspice toxfr` _transfer_format_file_ [_binary_format_file_]
+
+
+DESCRIPTION
+-----------
+**TOXFR** converts a SPICE binary format SPK, CK, PCK, DSK and EK file into
+a transfer file format that is used to transfer, or port, the binary data to
+a different computing environment. **TOXFR** requires at least the name of
+the input binary file, which is the first argument on the command line.
+Optionally, a name for the output transfer file may be specified as the
+second argument on the command line. If a name for the output file is
+provided on the command line it overrides the automatic naming conventions
+used by the program.
+
+If only the name of the input binary file is provided on the command line,
+**TOXFR** will generate a name for the output transfer file that has the
+same base name as the input binary file and an appropriate filename
+extension, based on the filename extension of the binary file. If **TOXFR**
+does not recognize the filename extension of the input binary file, or there
+is no filename extension on the input binary file, a filename extension of
+'.xfr' will be used as the filename extension of the output transfer file.
+If a file having the same name as the output file already exists, **TOXFR**
+signals an error and stops. Again, we assume that it is bad form to
+overwrite or replace an existing file.
+
+**TOXFR** recognizes the filename extensions ".bc", ".bee", ".bpc", and
+".bsp" which are associated with SPICE binary kernel files. These are
+converted to the transfer filename extensions ".xc", ".xee", ".xpc", and
+".xsp," respectively.
+
+**TOXFR** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice-version.1 b/debian/man/cspice-version.1
index b17b798..d537b4c 100644
--- a/debian/man/cspice-version.1
+++ b/debian/man/cspice-version.1
@@ -1,34 +1,37 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE-VERSION 1
-.SH NAME
-cspice-version \- prints the current version number of the SPICE Toolkit
-
-.SH SYNOPSIS
-\fBcspice-version\fR [\fIOPTIONS\fR]
-
-.SH DESCRIPTION
-.B cspice-version
-is a command-line program that prints the current version number of the SPICE Toolkit.
-.PP
-.B cspice-version
-is part of the SPICE Toolkit. See
-.BR cspice (7).
-
-.SH OPTIONS
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE\-VERSION" "1" "April 2017" "" "General Commands Manual"
+.
+.SH "NAME"
+\fBcspice\-version\fR \- prints version and details of the CSPICE Toolkit
+.
+.SH "SYNOPSIS"
+\fBcspice version\fR [\fIoptions\fR]
+.
+.SH "DESCRIPTION"
+\fBVERSION\fR is a command\-line program that prints the current version number of the SPICE Toolkit\.
+.
+.P
+\fBVERSION\fR is part of the CSPICE Toolkit\. See \fBcspice\fR(7) for more information\.
+.
+.SH "OPTIONS"
+To display only the SPICE toolkit version, VERSION should be executed without command arguments\.
+.
.TP
\fB\-a\fR, \fB\-all\fR
-Display all parameters for the environment for which the toolkit package was prepared, including SPICE toolkit version, system ID, operating system, compiler, and binary file format, max and min values for double precision and integer numbers.
+Display all parameters for the environment for which the toolkit package was prepared, including SPICE toolkit version, system ID, operating system, compiler, and binary file format, max and min values for double precision and integer numbers\.
+.
.TP
\fB\-v\fR, \fB\-version\fR
-Display the version of the version program.
+Display the version of the VERSION program\.
+.
.TP
\fB\-h\fR, \fB\-help\fR
-Display usage information.
-
-.SH SEE ALSO
-.BR cspice (7).
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+Display usage information\.
+.
+.SH "SEE ALSO"
+\fBcspice\fR(7)
+.
+.P
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice-version.md b/debian/man/cspice-version.md
new file mode 100644
index 0000000..17b4a17
--- /dev/null
+++ b/debian/man/cspice-version.md
@@ -0,0 +1,41 @@
+cspice-version(1) -- prints version and details of the CSPICE Toolkit
+=====================================================================
+
+SYNOPSIS
+--------
+`cspice version` [_options_]
+
+
+DESCRIPTION
+-----------
+**VERSION** is a command-line program that prints the current version number
+of the SPICE Toolkit.
+
+**VERSION** is part of the CSPICE Toolkit. See **cspice**(7) for more
+information.
+
+
+OPTIONS
+-------
+To display only the SPICE toolkit version, VERSION should be executed
+without command arguments.
+
+ * `-a`, `-all`:
+ Display all parameters for the environment for which the toolkit package
+ was prepared, including SPICE toolkit version, system ID, operating
+ system, compiler, and binary file format, max and min values for double
+ precision and integer numbers.
+
+ * `-v`, `-version`:
+ Display the version of the VERSION program.
+
+ * `-h`, `-help`:
+ Display usage information.
+
+
+SEE ALSO
+--------
+**cspice**(7)
+
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
diff --git a/debian/man/cspice.7 b/debian/man/cspice.7
index 6488123..c22d09f 100644
--- a/debian/man/cspice.7
+++ b/debian/man/cspice.7
@@ -1,81 +1,115 @@
-.\" Hey, EMACS: -*- nroff -*-
-.\" (C) Copyright 2016 Rock Storm <rockstorm at gmx.com>,
-.\"
-.TH CSPICE 7
-.SH NAME
-cspice \- contents summary of the SPICE Toolkit utilities
-
-.SH DESCRIPTION
-This documentation summarizes the different utilities comprising the SPICE Toolkit and a brief description of the various files where SPICE stores its data, often called "kernels" or "kernel files".
-
-.SH TOOLKIT UTILITIES
-.TP
-.B cspice-brief
-A command line utility used to summarize the information within an SPK file. See
-.BR cspice-brief (1).
-.TP
-.B cspice-chronos
-A utility used to convert time values between various formats, e.g. UTC to ET, Et to SCLK, etc. See
-.BR cspice-chronos (1).
-.TP
-.B cspice-ckbrief
-A command line utility used to summarize the pointing data within a CK file. See
-.BR cspice-ckbrief (1).
-.TP
-.B cspice-commnt
-A utility, usable in either interactive or command line mode, used to examine and manipulate the comment area of a SPICE binary kernel. See
-.BR cspice-commnt (1).
-.TP
-.B cspice-inspekt
-An interactive program used to examine and query to contents of an E-kernel. See
-.BR cspice-inspekt (1).
-.TP
-.B cspice-mkspk
-An application used to create, or append to, SPK files. See
-.BR cspice-mkspk (1).
-.TP
-.B cspice-spacit
-An interactive application used to manipulate and examine SPK files. See
-.BR cspice-spacit (1).
-.TP
-.B cspice-spkmerge
-An application used to merge several SPK files or subsets of SPK files into a single SPK file. See
-.BR cspice-spkmerge (1).
-.TP
-.B cspice-tobin
-A command line utility used to convert SPICE ASCII transfer files to architecture native binary kernels. See
-.BR cspice-tobin (1).
-.TP
-.B cspice-toxfr
-A command line utility used to convert SPICE binary kernels to ASCII transfer format. See
-.BR cspice-toxfr (1).
-.TP
-.B cspice-version
-A command line utility used to display the current version number of the SPICE Toolkit. See
-.BR cspice-version (1).
-
-.SH SPICE KERNELS
-SPICE kernels are composed of navigation and other ancillary information that has been structured and formatted for easy access and correct use by the planetary science and engineering communities. A kernel may store data in either text (ASCII) or binary format. SPICE kernel file contents are summarized below:
-.RS
-.PP
-\fISpacecraft and Planet Kernel\fR (\fBSPK\fR): spacecraft, planet, satellite, comet, or asteroid ephemerides, or more generally, location of any target body, given as a function of time.
-.PP
-\fIPlanetary Constants Kernel\fR (\fBPCK\fR): physical, dynamical and cartographic constants for target bodies, such as size and shape specifications, and orientation of the spin axis and prime meridian.
-.PP
-\fIInstrument Kernel\fR (\fBIK\fR): description kernel, containing descriptive data peculiar to a particular scientific instrument, such as field-of-view size, shape and orientation parameters.
-.PP
-\fIC-matrix Kernel\fR (\fBCK\fR): pointing kernel, containing a transformation, traditionally called the "C-matrix," which provides time-tagged pointing (orientation) angles for a spacecraft bus or a spacecraft structure upon which science instruments are mounted. A C-kernel may also include angular rate data for that structure.
-.PP
-\fIEvents Kernel\fR (\fBEK\fR): kernel summarizing mission activities - both planned and unanticipated. Events data consists of three components: science plans, sequences, and notes.
-.PP
-\fIFrames Kernel\fR (\fBFK\fR): contains specifications for the assortment of reference frames that are typically used by flight projects. This file also includes mounting alignment information for instruments, antennas and perhaps other structures of interest.
-.PP
-\fISpacecraft CLock Kernel\fR (\fBSCLK\fR): spacecraft's clock correlation data.
-.PP
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "CSPICE" "7" "April 2017" "" "CSPICE Toolkit"
+.
+.SH "NAME"
+\fBcspice\fR \- contents summary of the CSPICE Toolkit utilities
+.
+.SH "DESCRIPTION"
+This documentation summarizes the different utilities comprising the CSPICE Toolkit and a brief description of the various files where SPICE stores its data, often called "kernels" or "kernel files"\.
+.
+.SH "TOOLKIT UTILITIES"
+.
+.TP
+\fBBRIEF\fR
+A command\-line utility program that displays a contents and time coverage summary for one or more binary SPK or binary PCK files\. See \fBcspice\-brief\fR(1)\.
+.
+.TP
+\fBCHRONOS\fR
+A command\-line program that converts between several time systems and time formats, e\.g\. UTC to ET, ET to SCLK, etc\. See \fBcspice\-chronos\fR(1)\.
+.
+.TP
+\fBCKBRIEF\fR
+A command\-line utility program that displays a contents and time coverage summary for one or more binary CK files\. See \fBcspice\-ckbrief\fR(1)\.
+.
+.TP
+\fBCOMMNT\fR
+A command\-line program that reads, adds, extracts, or deletes comments from SPICE binary kernel files\. See \fBcspice\-commnt\fR(1)\.
+.
+.TP
+\fBDSKBRIEF\fR
+A command\-line utility program that displays a summary of the spatial coverage and additional attributes of one or more binary Digital Shape Kernel (DSK) files\. See \fBcspice\-dskbrief\fR(1)\.
+.
+.TP
+\fBDSKEXP\fR
+A command\-line program that exports data from DSK files to text files\. See \fBcspice\-dskexp\fR(1)\.
+.
+.TP
+\fBFRMDIFF\fR
+A program that samples orientation of a reference frame known to SPICE or computes differences between orientations of two reference frames known to SPICE, and either displays this orientation or these differences, or shows statistics about it or them\. See \fBcspice\-frmdiff\fR(1)\.
+.
+.TP
+\fBINSPEKT\fR
+An interactive program that examines the contents of an events component (ESQ) of an E\-kernel\. See \fBcspice\-inspekt\fR(1)\.
+.
+.TP
+\fBMKDSK\fR
+A utility program that creates a SPICE Digital Shape Kernel (DSK) file from a text file containing shape data for an extended object\. See \fBcspice\-mkdsk\fR(1)\.
+.
+.TP
+\fBMKSPK\fR
+A program that creates an SPK file from a text file containing trajectory information\. See \fBcspice\-mkspk\fR(1)\.
+.
+.TP
+\fBMSOPCK\fR
+A command\-line program that converts attitude data provided in a text file as UTC, SCLK, or ET\-tagged quaternions, Euler angles, or matrices, optionally accompanied by angular velocities, into a type 1, 2, or 3 SPICE C\-kernel\. See \fBcspice\-msopck\fR(1)\.
+.
+.TP
+\fBSPACIT\fR
+An interactive program that converts kernels in transfer format to binary format, converts binary kernels to transfer format, and summarizes the contents of binary kernels\. See \fBcspice\-spacit\fR(1)\.
+.
+.TP
+\fBSPKDIFF\fR
+Provides means for comparing the trajectories of two bodies or sampling the trajectory of a single body using data from SPICE kernels\. See \fBcspice\-spkdiff\fR(1)\.
+.
+.TP
+\fBSPKMERGE\fR
+A program that subsets or merges one or more SPK files into a single SPK file\. See \fBcspice\-spkmerge\fR(1)\.
+.
+.TP
+\fBTOBIN\fR
+A command\-line program that converts transfer format SPK, CK, PCK, DSK and EK files to binary format\. See \fBcspice\-tobin\fR(1)\.
+.
+.TP
+\fBTOXFR\fR
+A command\-line program that converts binary format SPK, CK, PCK, DSK and EK files to transfer format\. See \fBcspice\-toxfr\fR(1)\.
+.
+.TP
+\fBVERSION\fR
+A command line utility used to display the current version number of the SPICE Toolkit\. See \fBcspice\-version\fR(1)\.
+.
+.SH "SPICE KERNELS"
+SPICE kernels are composed of navigation and other ancillary information that has been structured and formatted for easy access and correct use by the planetary science and engineering communities\. A kernel may store data in either text (ASCII) or binary format\. SPICE kernel file contents are summarized below:
+.
+.IP "\(bu" 4
+\fISpacecraft and Planet Kernel\fR (\fBSPK\fR): Spacecraft, planet, satellite, comet, or asteroid ephemerides, or more generally, location of any target body, given as a function of time\.
+.
+.IP "\(bu" 4
+\fIPlanetary Constants Kernel\fR (\fBPCK\fR): Physical, dynamical and cartographic constants for target bodies, such as size and shape specifications, and orientation of the spin axis and prime meridian\.
+.
+.IP "\(bu" 4
+\fIInstrument Kernel\fR (\fBIK\fR): Description kernel, containing descriptive data peculiar to a particular scientific instrument, such as field\-of\-view size, shape and orientation parameters\.
+.
+.IP "\(bu" 4
+\fIC\-matrix Kernel\fR (\fBCK\fR): Pointing kernel, containing a transformation, traditionally called the "C\-matrix," which provides time\-tagged pointing (orientation) angles for a spacecraft bus or a spacecraft structure upon which science instruments are mounted\. A C\-kernel may also include angular rate data for that structure\.
+.
+.IP "\(bu" 4
+\fIEvents Kernel\fR (\fBEK\fR): Kernel summarizing mission activities \- both planned and unanticipated\. Events data consists of three components: science plans, sequences, and notes\.
+.
+.IP "\(bu" 4
+\fIFrames Kernel\fR (\fBFK\fR): Contains specifications for the assortment of reference frames that are typically used by flight projects\. This file also includes mounting alignment information for instruments, antennas and perhaps other structures of interest\.
+.
+.IP "\(bu" 4
+\fISpacecraft CLock Kernel\fR (\fBSCLK\fR): Spacecraft\'s clock correlation data\.
+.
+.IP "\(bu" 4
\fILeap Seconds Kernel\fR (\fBLSK\fR)
-.PP
-\fIDigital Shape Kernel\fR (\fBDSK\fR): digital shape model for both small, irregularly shaped bodies such as asteroids and comet nuclei, and for large, more uniformly shaped bodies such as the moon, earth and Mars.
-.RE
-
-.SH AUTHOR
-This manual page was written by Rock Storm <rockstorm at gmx.com> based on the official SPICE documentation. See http://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/index.html for more information.
+.
+.IP "\(bu" 4
+\fIDigital Shape Kernel\fR (\fBDSK\fR): Digital shape model for both small, irregularly shaped bodies such as asteroids and comet nuclei, and for large, more uniformly shaped bodies such as the moon, earth and Mars\.
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+Full documentation is provided by package cspice\-doc on /usr/share/doc/cspice or it can be obtained online on https://naif\.jpl\.nasa\.gov/pub/naif/toolkit_docs/C/\.
diff --git a/debian/man/cspice.md b/debian/man/cspice.md
new file mode 100644
index 0000000..c90dddc
--- /dev/null
+++ b/debian/man/cspice.md
@@ -0,0 +1,142 @@
+cspice(7) -- contents summary of the CSPICE Toolkit utilities
+=============================================================
+
+
+DESCRIPTION
+-----------
+This documentation summarizes the different utilities comprising the CSPICE
+Toolkit and a brief description of the various files where SPICE stores its
+data, often called "kernels" or "kernel files".
+
+
+TOOLKIT UTILITIES
+-----------------
+
+ * `BRIEF`:
+ A command-line utility program that displays a contents and time coverage
+ summary for one or more binary SPK or binary PCK files. See
+ **cspice-brief**(1).
+
+ * `CHRONOS`:
+ A command-line program that converts between several time systems and time
+ formats, e.g. UTC to ET, ET to SCLK, etc. See **cspice-chronos**(1).
+
+ * `CKBRIEF`:
+ A command-line utility program that displays a contents and time coverage
+ summary for one or more binary CK files. See **cspice-ckbrief**(1).
+
+ * `COMMNT`:
+ A command-line program that reads, adds, extracts, or deletes comments from
+ SPICE binary kernel files. See **cspice-commnt**(1).
+
+ * `DSKBRIEF`:
+ A command-line utility program that displays a summary of the spatial
+ coverage and additional attributes of one or more binary Digital Shape
+ Kernel (DSK) files. See **cspice-dskbrief**(1).
+
+ * `DSKEXP`:
+ A command-line program that exports data from DSK files to text files. See
+ **cspice-dskexp**(1).
+
+ * `FRMDIFF`:
+ A program that samples orientation of a reference frame known to SPICE or
+ computes differences between orientations of two reference frames known to
+ SPICE, and either displays this orientation or these differences, or shows
+ statistics about it or them. See **cspice-frmdiff**(1).
+
+ * `INSPEKT`:
+ An interactive program that examines the contents of an events component
+ (ESQ) of an E-kernel. See **cspice-inspekt**(1).
+
+ * `MKDSK`:
+ A utility program that creates a SPICE Digital Shape Kernel (DSK) file from
+ a text file containing shape data for an extended object. See
+ **cspice-mkdsk**(1).
+
+ * `MKSPK`:
+ A program that creates an SPK file from a text file containing trajectory
+ information. See **cspice-mkspk**(1).
+
+ * `MSOPCK`:
+ A command-line program that converts attitude data provided in a text file
+ as UTC, SCLK, or ET-tagged quaternions, Euler angles, or matrices,
+ optionally accompanied by angular velocities, into a type 1, 2, or 3 SPICE
+ C-kernel. See **cspice-msopck**(1).
+
+ * `SPACIT`:
+ An interactive program that converts kernels in transfer format to binary
+ format, converts binary kernels to transfer format, and summarizes the
+ contents of binary kernels. See **cspice-spacit**(1).
+
+ * `SPKDIFF`:
+ Provides means for comparing the trajectories of two bodies or sampling the
+ trajectory of a single body using data from SPICE kernels. See
+ **cspice-spkdiff**(1).
+
+ * `SPKMERGE`:
+ A program that subsets or merges one or more SPK files into a single SPK
+ file. See **cspice-spkmerge**(1).
+
+ * `TOBIN`:
+ A command-line program that converts transfer format SPK, CK, PCK, DSK and
+ EK files to binary format. See **cspice-tobin**(1).
+
+ * `TOXFR`:
+ A command-line program that converts binary format SPK, CK, PCK, DSK and EK
+ files to transfer format. See **cspice-toxfr**(1).
+
+ * `VERSION`:
+ A command line utility used to display the current version number of the
+ SPICE Toolkit. See **cspice-version**(1).
+
+
+SPICE KERNELS
+-------------
+SPICE kernels are composed of navigation and other ancillary information that has been structured and formatted for easy access and correct use by the planetary science and engineering communities. A kernel may store data in either text (ASCII) or binary format. SPICE kernel file contents are summarized below:
+
+ * _Spacecraft and Planet Kernel_ (**SPK**):
+ Spacecraft, planet, satellite, comet, or asteroid ephemerides, or more
+ generally, location of any target body, given as a function of time.
+
+ * _Planetary Constants Kernel_ (**PCK**):
+ Physical, dynamical and cartographic constants for target bodies, such as
+ size and shape specifications, and orientation of the spin axis and prime
+ meridian.
+
+ * _Instrument Kernel_ (**IK**):
+ Description kernel, containing descriptive data peculiar to a particular
+ scientific instrument, such as field-of-view size, shape and orientation
+ parameters.
+
+ * _C-matrix Kernel_ (**CK**):
+ Pointing kernel, containing a transformation, traditionally called the
+ "C-matrix," which provides time-tagged pointing (orientation) angles for a
+ spacecraft bus or a spacecraft structure upon which science instruments are
+ mounted. A C-kernel may also include angular rate data for that structure.
+
+ * _Events Kernel_ (**EK**):
+ Kernel summarizing mission activities - both planned and unanticipated.
+ Events data consists of three components: science plans, sequences, and
+ notes.
+
+ * _Frames Kernel_ (**FK**):
+ Contains specifications for the assortment of reference frames that are
+ typically used by flight projects. This file also includes mounting
+ alignment information for instruments, antennas and perhaps other
+ structures of interest.
+
+ * _Spacecraft CLock Kernel_ (**SCLK**):
+ Spacecraft's clock correlation data.
+
+ * _Leap Seconds Kernel_ (**LSK**)
+
+ * _Digital Shape Kernel_ (**DSK**):
+ Digital shape model for both small, irregularly shaped bodies such as
+ asteroids and comet nuclei, and for large, more uniformly shaped bodies
+ such as the moon, earth and Mars.
+
+
+SEE ALSO
+--------
+Full documentation is provided by package cspice-doc on /usr/share/doc/cspice
+or it can be obtained online on https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/C/.
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-astro/packages/cspice.git
More information about the Debian-astro-commits
mailing list