auto-regenerate man/html pages

1 files changed, 21 insertions, 13 deletions

diff --git a/cuerecover.html b/cuerecover.html
index a82e423..7de40e0 100644
--- a/cuerecover.html
+++ b/cuerecover.html
@@ -5,7 +5,7 @@
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 <meta name="generator" content="Docutils 0.14: http://docutils.sourceforge.net/" />
 <title>cuerecover</title>
-<meta name="date" content="2020-05-11" />
+<meta name="date" content="2020-05-12" />
 <style type="text/css">
 
 /*
@@ -373,7 +373,7 @@ ul.auto-toc {
 <tr class="manual-group field"><th class="docinfo-name">Manual group:</th><td class="field-body">Urchlay</td>
 </tr>
 <tr><th class="docinfo-name">Date:</th>
-<td>2020-05-11</td></tr>
+<td>2020-05-12</td></tr>
 <tr><th class="docinfo-name">Version:</th>
 <td>0.1.0</td></tr>
 </tbody>
@@ -385,14 +385,12 @@ ul.auto-toc {
 <!-- into git since we don't want to require our users to have rst2man.py. -->
 <div class="section" id="synopsis">
 <h1>SYNOPSIS</h1>
-<p>cuerecover [-s sec] <strong>bin-file</strong> [<strong>bin-file</strong> ...]</p>
+<p>cuerecover [-o output] [-s sec] [-t thresh] <strong>bin-file</strong> [<strong>bin-file</strong> ...]</p>
 </div>
 <div class="section" id="description">
 <h1>DESCRIPTION</h1>
 <p>cuerecover attempts to generate a usable cue sheet for CD images which
-are missing their .cue (or .ccd, .mds, etc) files. The generated cue
-sheet is written to standard output [*], so add e.g. &quot;&gt; filename.cue&quot;
-to redirect it to a file.</p>
+are missing their .cue (or .ccd, .mds, etc) files.</p>
 <p>If a single .bin file is given, it's assumed to hold all the tracks (which
 might only be one). If multiple .bin files are given, each one is assumed to
 represent one track of the same CD image.</p>
@@ -418,13 +416,20 @@ messages are printed to standard error.</p>
 <kbd><span class="option">--help</span></kbd></td>
 <td>Print short usage string.</td></tr>
 <tr><td class="option-group">
+<kbd><span class="option">-o <var>&lt;file&gt;</var></span></kbd></td>
+<td>Write cue file to <em>file</em> rather than standard output. If
+<em>file</em> already exists, cuerecover will refuse to overwrite it,
+which makes this safer than redirecting stdout.</td></tr>
+<tr><td class="option-group">
 <kbd><span class="option">-s <var>&lt;sec&gt;</var></span></kbd></td>
 <td>Minimum amount of silence for detecting the split point between
-two audio tracks (default: 2). Argument is in seconds, and
-non-integers are allowed. 0 means to disable splitting tracks:
-all the audio tracks will be combined into one in the .cue
-sheet. This option is ignored when multiple .bin file arguments
-are given, since they're already split into tracks.</td></tr>
+two audio tracks. Argument is in seconds, and decimals
+are allowed. The default is 2, which is the standard sized
+gap between tracks in the Redbook standard and in most CD
+authoring software. 0 means to disable splitting tracks:
+all the audio tracks will be combined into one in the
+.cue sheet. This option is ignored when multiple .bin file
+arguments are given, since they're already split into tracks.</td></tr>
 <tr><td class="option-group">
 <kbd><span class="option">-t <var>&lt;thresh&gt;</var></span></kbd></td>
 <td>Silence threshold, 0 to 100. Default is 0. This is
@@ -432,7 +437,9 @@ the percentage of non-zero bytes allowed in a sector for it
 to be considered silent. Sometimes audio tracks have random
 data in the pregap (before the INDEX 01), which will fool
 cuerecover into thinking there's no pregap. This option can
-help with those, but don't set it too high.</td></tr>
+help with those, but don't set it too high. This option is ignored
+when multiple .bin file arguments are given, since they're already
+split into tracks.</td></tr>
 <tr><td class="option-group">
 <kbd><span class="option">-v</span></kbd></td>
 <td>Verbose mode. Prints (on stderr) some extra messages about what
@@ -456,7 +463,8 @@ data tracks that aren't the first track on the disc.</li>
 <li>If there's a data track, it's a raw image (2352 bytes per sector, includes
 the sync pulse, address, CRC, ECC, etc). If the data track was stored as
 'cooked' data (2048 bytes/sector, MODE1/2048 in the original .cue file),
-it'll be treated as an audio track. You can check for this by trying to
+it'll be treated as an audio track, and you'll get a warning that it
+looks like 'cooked' data. You can check for this by trying to
 mount the .bin file as an ISO or HFS image: if it mounts, the first
 track is 'cooked'. It'll also be obvious if you use the .cue sheet to
 extract the image into files: ISO images don't sound musical at all!</li>