Update text files for 1.1.1RC2

Closes #671

.gitignore

@@ -10,17 +10,14 @@ srcdist/
 # Generated email templates
 email/*.tmpl
 
-# Romanian ro.po is generated from ro.px, due to mapping to latin-1
-ro.po
-
 # Build results
 SABnzbd*.zip
 SABnzbd*.exe
 SABnzbd*.gz
 SABnzbd*.dmg
 
-# WingIDE project file
-*.wpr
+# WingIDE project files
+*.wp[ru]
 
 # General junk
 *.keep

INSTALL.txt

@@ -1,5 +1,4 @@
-                                SABnzbd 1.1.0
-
+                                SABnzbd 1.1.1
 -------------------------------------------------------------------------------
 0) LICENSE
 -------------------------------------------------------------------------------

ISSUES.txt

@@ -12,7 +12,7 @@
   Windows-only:
   If you keep having trouble with par2 multicore you can disable it
   in Config->Switches.
-  This will force the use of the old and tried, but slower par2-classic program.
+  This will force the use of the old and tried, but slower par2cmdline program.
 
 - A bug in Windows 7 may cause severe memory leaks when you use SABnzbd in
   combination with some virus scanners and firewalls.

PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 1.0
 Name: SABnzbd
-Version: 1.2.0
-Summary: SABnzbd-1.2.0
+Version: 1.1.1RC2
+Summary: SABnzbd-1.1.1RC2
 Home-page: http://sabnzbd.org
 Author: The SABnzbd Team
 Author-email: team@sabnzbd.org

README.mkd

@@ -1,14 +1,26 @@
-Release Notes  -  SABnzbd 1.2.0
-===============================
+Release Notes  -  SABnzbd 1.1.1RC2
+==================================
 
-## What's new in 1.2.0
+## What's new in 1.1.1RC2
+
+## Bug fixes
+- Fixed email notifications to smtp2go.com (and possibly others)
+- Replaced par2-classic with par2cmdline (will fix some verification hangups)
+- Fix problem with Config pages on mobile browsers
+- Updated INSTALL.txt
+
+
+## What's new in 1.1.1RC1
 
 
 ## Changes:
+- Button to regenerate a self-signed HTTPS certificate (to update to modern standards)
 
 
 ## Bug fixes
-
+- Restored download speed for Unix (and some other) systems
+- Fixed yEnc crash that occurred on some Windows systems
+- Small UI fixes
 
 
 ## About

SABnzbd.py

@@ -480,7 +480,7 @@ def print_modules():
         logging.error(T('par2 binary... NOT found!'))
 
     if sabnzbd.newsunpack.PAR2C_COMMAND:
-        logging.info("par2-classic binary... found (%s)", sabnzbd.newsunpack.PAR2C_COMMAND)
+        logging.info("par2cmdline binary... found (%s)", sabnzbd.newsunpack.PAR2C_COMMAND)
 
     if sabnzbd.newsunpack.RAR_COMMAND:
         logging.info("UNRAR binary... found (%s)", sabnzbd.newsunpack.RAR_COMMAND)

interfaces/Config/templates/config_general.tmpl

@@ -170,10 +170,15 @@
         </div><!-- /col2 -->
         <div class="col1">
             <fieldset>
-                <div class="field-pair">
-                    <label class="config" for="bandwidth_max">$T('opt-bandwidth_max')</label>
-                    <input type="text" name="bandwidth_max" id="bandwidth_max" value="$bandwidth_max" class="smaller_input" />
-                    <span class="desc">$T('explain-bandwidth_max')<br />$T('wizard-bandwidth-explain')</span>
+                <div class="field-pair value-and-select">
+                    <label class="config" for="bandwidth_max_value">$T('opt-bandwidth_max')</label>
+                    <input type="number" name="bandwidth_max_value" id="bandwidth_max_value" class="smaller_input" />
+                    <select name="bandwidth_max_dropdown" id="bandwidth_max_dropdown">
+                        <option value="">B/s</option>
+                        <option value="K">KB/s</option>
+                        <option value="M" selected>MB/s</option>
+                    </select>
+                    <input type="hidden" name="bandwidth_max" id="bandwidth_max" value="$bandwidth_max" />
                 </div>
                 <div class="field-pair">
                     <label class="config" for="bandwidth_perc">$T('opt-bandwidth_perc')</label>
@@ -282,6 +287,22 @@
     if(\$('#https_cert').val() != 'server.cert') {
         \$('.generate_cert').attr('disabled', 'disabled')
     }
+
+    // Parse the text
+    var bandwidthLimit = \$('#bandwidth_max').val()
+    if(bandwidthLimit) {
+        var bandwithLimitNumber = parseFloat(bandwidthLimit)
+        var bandwithLimitText = bandwidthLimit.replace(/[^a-zA-Z]+/g, '');
+        \$('#bandwidth_max_value').val(bandwithLimitNumber)
+        \$('#bandwidth_max_dropdown').val(bandwithLimitText)
+    }
+    
+
+    // Update the value
+    \$('#bandwidth_max_value, #bandwidth_max_dropdown').on('change', function() {
+        \$('#bandwidth_max').val(\$('#bandwidth_max_value').val() + \$('#bandwidth_max_dropdown').val())
+    })
+
 });
 </script>
 

interfaces/Config/templates/config_server.tmpl

@@ -279,8 +279,8 @@
             this.submit()
         })
     })
-    
-    /** 
+
+    /**
         Color the priority labels
     **/
     // They are already sorted
@@ -298,7 +298,7 @@
         \$(this).css('background-color', theColor)
     })
 
-    /** 
+    /**
         Message on no Default category selected
     **/
     function checkServerCats() {
@@ -309,10 +309,10 @@
             // See if this server is enabled
             if(!\$(this).parents('.section').find('.col2').hasClass('server-disabled') ) {
                 // Is there Default?
-                if(\$(this).val().indexOf('Default') > -1) {
+                if(\$(this).val() && \$(this).val().indexOf('Default') > -1) {
                     // Hide
                     \$('.alert-no-category').hide()
-                    hasDefault = true 
+                    hasDefault = true
                     // All good!
                     return true
                 }
@@ -323,8 +323,8 @@
     }
 
     \$('select[name="categories"]').on('change', checkServerCats)
-    checkServerCats()    
-    
+    checkServerCats()
+
     /**
         Click events
     **/

interfaces/Config/templates/staticcfg/css/style.css

@@ -969,6 +969,12 @@ input[type="checkbox"] {
 .main-restarting small {
     font-size: 3rem !important;
 }
+.value-and-select input {
+    margin-right: -5px;
+}
+.value-and-select select {
+    min-width: 30px;
+}
 
 .dotOne, .dotTwo, .dotThree {
     opacity: 0;
@@ -1072,6 +1078,10 @@ input[type="checkbox"] {
         display: inline-block;
         margin-right: 0.5em;
     }
+
+    .navbar .nav>li>a {
+        height: auto;
+    }
     
     .section .col2 h3 {
         padding-right: 25px;

sabnzbd/database.py

@@ -397,7 +397,7 @@ class HistoryDB(object):
                 pp = items.get('pp')
                 script = items.get('script')
                 cat = items.get('category')
-            except AttributeError:
+            except (AttributeError, IndexError):
                 return '', '', '', '', ''
         return dtype, url, pp, script, cat
 

sabnzbd/emailer.py

@@ -44,22 +44,25 @@ def errormsg(msg):
 def send(message, email_to, test=None):
     """ Send message if message non-empty and email-parms are set """
 
+    def utf8(p):
+        return p.encode('utf8', 'ignore')
+
     # we should not use CFG if we are testing. we should use values
     # from UI instead.
 
     if test:
-        email_server = test.get('email_server')
-        email_from = test.get('email_from')
-        email_account = test.get('email_account')
-        email_pwd = test.get('email_pwd')
+        email_server = utf8(test.get('email_server'))
+        email_from = utf8(test.get('email_from'))
+        email_account = utf8(test.get('email_account'))
+        email_pwd = utf8(test.get('email_pwd'))
         if email_pwd and not email_pwd.replace('*', ''):
             # If all stars, get stored password instead
-            email_pwd = cfg.email_pwd()
+            email_pwd = utf8(cfg.email_pwd())
     else:
-        email_server = cfg.email_server()
-        email_from = cfg.email_from()
-        email_account = cfg.email_account()
-        email_pwd = cfg.email_pwd()
+        email_server = utf8(cfg.email_server())
+        email_from = utf8(cfg.email_from())
+        email_account = utf8(cfg.email_account())
+        email_pwd = utf8(cfg.email_pwd())
 
     # email_to is replaced at send_with_template, since it can be an array
 

sabnzbd/newsunpack.py

@@ -122,7 +122,7 @@ def find_programs(curdir):
             sabnzbd.newsunpack.PAR2_COMMAND = check(curdir, 'win/par2/par2.exe')
         if not sabnzbd.newsunpack.RAR_COMMAND:
             sabnzbd.newsunpack.RAR_COMMAND = check(curdir, 'win/unrar/UnRAR.exe')
-        sabnzbd.newsunpack.PAR2C_COMMAND = check(curdir, 'win/par2/par2-classic.exe')
+        sabnzbd.newsunpack.PAR2C_COMMAND = check(curdir, 'win/par2/par2cmdline.exe')
         sabnzbd.newsunpack.ZIP_COMMAND = check(curdir, 'win/unzip/unzip.exe')
         sabnzbd.newsunpack.SEVEN_COMMAND = check(curdir, 'win/7zip/7za.exe')
     else:
@@ -1070,7 +1070,7 @@ def par2_repair(parfile_nzf, nzo, workdir, setname, single):
             if os.path.exists(test_parfile):
                 parfile = test_parfile
                 break
-    
+
     parfile = short_path(parfile)
     workdir = short_path(workdir)
 
@@ -1240,7 +1240,7 @@ def PAR_Verify(parfile, parfile_nzf, nzo, setname, joinables, classic=False, sin
         # Allow options if not classic or when classic and non-classic are the same
         if options and (not classic or (PAR2_COMMAND == PAR2C_COMMAND)):
             command.insert(2, options)
-    logging.debug('Par2-classic = %s', classic)
+    logging.debug('Par2-classic/cmdline = %s', classic)
 
     # Append the wildcard for this set
     parfolder = os.path.split(parfile)[0]
@@ -1572,7 +1572,7 @@ def PAR_Verify(parfile, parfile_nzf, nzo, setname, joinables, classic=False, sin
         used_joinables.extend(reconstructed)
 
     if retry_classic:
-        logging.debug('Retry PAR2-joining with par2-classic')
+        logging.debug('Retry PAR2-joining with par2-classic/cmdline')
         return PAR_Verify(parfile, parfile_nzf, nzo, setname, joinables, classic=True, single=single)
     else:
         return finished, readd, pars, datafiles, used_joinables, used_par2

sabnzbd/skintext.py

@@ -344,7 +344,6 @@ SKIN_TEXT = {
     'opt-rss_rate' : TT('RSS Checking Interval'),
     'explain-rss_rate' : TT('Checking interval (in minutes, at least 15). Not active when you use the Scheduler!'),
     'opt-bandwidth_max' : TT('Maximum line speed'),
-    'explain-bandwidth_max' : TT('Highest possible linespeed in Bytes/second, e.g. 2M.'),
     'opt-bandwidth_perc' : TT('Percentage of line speed'),
     'explain-bandwidth_perc' : TT('Which percentage of the linespeed should SABnzbd use, e.g. 50'),
     'opt-cache_limitstr' : TT('Article Cache Limit'),
@@ -972,7 +971,6 @@ SKIN_TEXT = {
     'wizard-goto' :  TT('Go to SABnzbd'), #: Wizard step
     'wizard-exit' : TT('Exit SABnzbd'), #: Wizard EXIT button on first page
     'wizard-start' : TT('Start Wizard'), #: Wizard START button on first page
-    'wizard-bandwidth-explain' : TT('When your ISP speed is 10 Mbits/sec, enter here 1M'), #: Wizard explain relation bits/sec bytes/sec
 
 #Special
     'yourRights' : TT('''

sabnzbd/tvsort.py

@@ -207,7 +207,7 @@ class SeriesSorter(object):
                 # First check if the show matches TV episode regular expressions. Returns regex match object
                 self.match_obj, self.extras = check_regexs(self.original_dirname, series_match)
                 if self.match_obj:
-                    logging.debug("Found TV Show - Starting folder sort (%s)", self.original_dirname)
+                    logging.debug("Found TV Show (%s)", self.original_dirname)
                     self.matched = True
 
     def is_match(self):
@@ -524,7 +524,7 @@ class GenericSorter(object):
         if force or (cfg.enable_movie_sorting() and self.sort_string):
             # First check if the show matches TV episode regular expressions. Returns regex match object
             if force or (self.cat and self.cat.lower() in self.cats) or (not self.cat and 'None' in self.cats):
-                logging.debug("Movie Sorting - Starting folder sort (%s)", self.original_dirname)
+                logging.debug("Found Movie (%s)", self.original_dirname)
                 self.matched = True
 
     def get_final_path(self):
@@ -728,7 +728,7 @@ class DateSorter(object):
             if force or (self.cat and self.cat.lower() in self.cats) or (not self.cat and 'None' in self.cats):
                 self.match_obj, self.date_type = check_for_date(self.original_dirname, date_match)
                 if self.match_obj:
-                    logging.debug("Date Sorting - Starting folder sort (%s)", self.original_dirname)
+                    logging.debug("Found date for sorting (%s)", self.original_dirname)
                     self.matched = True
 
     def is_match(self):

win/par2/README_par2cmdline.txt

@@ -0,0 +1,336 @@
+par2cmdline is a PAR 2.0 compatible file verification and repair tool.
+
+To see the ongoing development see
+https://github.com/BlackIkeEagle/par2cmdline
+
+The original development was done on Sourceforge but stalled.
+For more information from the original authors see
+http://parchive.sourceforge.net
+Also for details of the PAR 2.0 specification and discussion of all 
+things PAR.
+
+WHAT EXACTLY IS PAR2CMDLINE?
+
+par2cmdline is a program for creating and using PAR2 files to detect
+damage in data files and repair them if necessary. It can be used with
+any kind of file.
+
+WHY IS PAR 2.0 better than PAR 1.0?
+
+ * It is not necessary to split a single large file into many equally
+   size small files (although you can still do so if you wish).
+
+ * There is no loss of efficiency when operating on multiple files
+   of different sizes.
+
+ * It is possible to repair damaged files (using exactly the amount of
+   recovery data that corresponds to the amount of damage), rather than
+   requiring the complete reconstruction of the damaged file.
+
+ * Recovery files may be of different sizes making it possible to
+   obtain exactly the amount of recovery data required to carry out
+   a repair.
+
+ * Because damaged data files are still useable during the recovery
+   process, less recovery data is required to achieve a successful
+   repair. It is therefore not necessary to create as much recovery
+   data in the first place to achieve the same level of protection.
+
+ * You can protect up to 32768 files rather than the 256 that PAR 1.0
+   is limited to.
+
+ * Damaged or incomplete recovery files can also be used during the
+   recovery process in the same way that damaged data files can.
+
+ * PAR 2.0 requires less recovery data to provide the same level of 
+   protection from damage compared with PAR 1.0.
+
+DOES PAR 2.0 HAVE ANY DISADVANTAGES?
+
+Yes, there is one disadvantage:
+
+ * All PAR 2.0 program will take somewhat longer to create recovery
+   files than a PAR 1.0 program does.
+
+This disadvantage is considerably mitigated by the fact that you don't
+need to create as much recovery data in the first place to provide the
+same level of protection against loss and damage.
+
+COMPILING PAR2CMDLINE
+
+You should have received par2cmdline in the form of source code which
+you can compile on your computer. You may optionally have received a
+precompiled version of the program for your operating system.
+
+If you have only downloaded a precompiled executable, then the source
+code should be available from the same location where you downloaded the
+executable from.
+
+If you have MS Visual Studio .NET, then just open the par2cmdline.sln
+file and compile. You should then copy par2cmdline.exe to an appropriate
+location that is on your path.
+
+To compile on Linux and other Unix variants use the following commands:
+
+  aclocal
+  automake --add-missing
+  autoconf
+  ./configure
+  make
+  make check
+  make install
+
+See INSTALL for full details on how to use the "configure" script.
+
+USING PAR2CMDLINE
+
+The command line parameters for par2cmdline are as follow:
+
+    par2 -h  : show this help
+    par2 -V  : show version
+    par2 -VV : show version and copyright
+
+    par2 c(reate) [options] <par2 file> [files]
+    par2 v(erify) [options] <par2 file> [files]
+    par2 r(epair) [options] <par2 file> [files]
+
+  Also:
+
+    par2create [options] <par2 file> [files]
+    par2verify [options] <par2 file> [files]
+    par2repair [options] <par2 file> [files]
+
+  Options:
+
+    -a<file> : Set the main par2 archive name
+               required on create, optional for verify and repair
+    -b<n>    : Set the Block-Count
+    -s<n>    : Set the Block-Size (Don't use both -b and -s)
+    -r<n>    : Level of Redundancy (%)
+    -r<c><n> : Redundancy target size, <c>=g(iga),m(ega),k(ilo) bytes
+    -c<n>    : Recovery block count (don't use both -r and -c)
+    -f<n>    : First Recovery-Block-Number
+    -u       : Uniform recovery file sizes
+    -l       : Limit size of recovery files (Don't use both -u and -l)
+    -n<n>    : Number of recovery files (Don't use both -n and -l)
+    -m<n>    : Memory (in MB) to use
+    -v [-v]  : Be more verbose
+    -q [-q]  : Be more quiet (-qq gives silence)
+    -p       : Purge backup files and par files on successful recovery or
+               when no recovery is needed
+    -R       : Recurse into subdirectories (only useful on create)
+    -N       : No data skipping (find badly misspositioned data blocks)
+    -S<n>    : Skip leaway (distance +/- from expected block position)
+    --       : Treat all remaining CommandLine as filenames
+
+If you wish to create par2 files for a single source file, you may leave
+out the name of the par2 file from the command line. par2cmdline will then
+assume that you wish to base the filenames for the par2 files on the name
+of the source file.
+
+You may also leave off the .par2 file extension when verifying and repairing.
+
+CREATING PAR2 FILES
+
+With PAR 2.0 you can create PAR2 recovery files for as few as 1 or as many as
+32768 files. If you wanted to create PAR1 recovery files for a single file
+you were forced to split the file into muliple parts and RAR was frequently
+used for this purpose. You do NOT need to split files with PAR 2.0.
+
+To create PAR 2 recovery files for a single data file (e.g. one called
+test.mpg), you can use the following command:
+
+  par2 create test.mpg.par2 test.mpg
+
+If test.mpg is an 800 MB file, then this will create a total of 8 PAR2 files
+with the following filenames (taking roughly 6 minutes on a PC with a
+1500MHz CPU):
+
+  test.mpg.par2          - This is an index file for verification only
+  test.mpg.vol00+01.par2 - Recovery file with 1 recovery block
+  test.mpg.vol01+02.par2 - Recovery file with 2 recovery blocks
+  test.mpg.vol03+04.par2 - Recovery file with 4 recovery blocks
+  test.mpg.vol07+08.par2 - Recovery file with 8 recovery blocks
+  test.mpg.vol15+16.par2 - Recovery file with 16 recovery blocks
+  test.mpg.vol31+32.par2 - Recovery file with 32 recovery blocks
+  test.mpg.vol63+37.par2 - Recovery file with 37 recovery blocks
+
+The test.mpg.par2 file is 39 KB in size and the other files vary in size from
+443 KB to 15 MB.
+
+These par2 files will enable the recovery of up to 100 errors totalling 40 MB
+of lost or damaged data from the original test.mpg file when it and the par2
+files are posted on UseNet.
+
+When posting on UseNet it is recommended that you use the "-s" option to set
+a blocksize that is equal to the Article size that you will use to post the
+data file. If you wanted to post the test.mpg file using an article size
+of 300 KB then the command you would type is:
+
+  par2 create -s307200 test.mpg.par2 test.mpg
+
+This will create 9 PAR2 files instead of 8, and they will be capable of
+correcting up to 134 errors totalling 40 MB. It will take roughly 8 minutes
+to create the recovery files this time.
+
+In both of these two examples, the total quantity of recovery data created
+was 40 MB (which is 5% of 800 MB). If you wish to create a greater or lesser
+quantity of recovery data, you can use the "-r" option.
+
+To create 10% recovery data instead of the default of 5% and also to use a
+block size of 300 KB, you would use the following command:
+
+  par2 create -s307200 -r10 test.mpg.par2 test.mpg
+
+This would also create 9 PAR2 files, but they would be able to correct up to
+269 errors totalling 80 MB. Since twice as much recovery data is created, it
+will take about 16 minutes to do so with a 1500MHz CPU.
+
+The "-u" and "-n" options can be used to control exactly how many recovery
+files are created and how the recovery blocks are distributed among them.
+They do not affect the total quantity of recovery data created.
+
+The "-f" option is used when you create additional recovery data e.g. If 
+you have already created 10% and want another 5% then you migh use the 
+following command:
+
+  par2 create -s307200 -r5 -f300 test.mpg.par2 test.mpg
+
+This specifies the same block size (which is a requirement for additional
+recovery files), 5% recovery data, and a first block number of 300.
+
+The "-m" option controls how much memory par2cmdline uses. It defaults to
+16 MB unless you override it.
+
+When creating PAR2 recovery files you might want to fill up a "medium" like a
+DVD or a Blu-Ray. Therefore we can set the target size of the recovery files by
+issuing the following command:
+
+  par2 create -rm200 recovery.par2 *
+
+It makes no sense to set a insanely high recovery size. The command will make
+that the resulting sum of the par2 files approaches the requested size. It is
+an estimate so don't go to crazy.
+
+CREATING PAR2 FILES FOR MULTIPLE DATA FILES
+
+When creating PAR2 recovery files from multiple data files, you must specify
+the base filename to use for the par2 files and the names of all of the data
+files.
+
+If test.mpg had been split into multiple RAR files, then you could use:
+
+  par2 create test.mpg.rar.par2 test.mpg.part*.rar
+
+The files filename "test.mpg.rar.par2" says what you want the par2 files to
+be called and "test.mpg.part*.rar" should select all of the RAR files.
+
+VERIFYING AND REPAIRING
+
+When using par2 recovery files to verify or repair the data files from
+which they were created, you only need to specify the filename of one
+of the par2 files to par2cmdline.
+
+e.g.:
+
+  par2 verify test.mpg.par2
+
+This tells par2cmdline to use the information in test.mpg.par2 to verify the
+data files.
+
+par2cmdline will automatically search for the other par2 files that were
+created and use the information they contain to determine the filenames
+of the original data files and then to verify them.
+
+If all of the data files are OK, then par2cmdline will report that repair
+will not be required.
+
+If any of the data files are missing or damaged, par2cmdline will report
+the details of what it has found. If the recovery files contain enough
+recovery blocks to repair the damage, you will be told that repair is
+possible. Otherwise you will be told exactly how many recovery blocks
+will be required in order to repair.
+
+To carry out a repair use the following command:
+
+  par2 repair test.mpg.par2
+
+This tells par2cmdline to verify and if possible repair any damaged or
+missing files. If a repair is carried out, then each file which is
+repaired will be re-verified to confirm that the repair was successful.
+
+MISNAMED AND INCOMPLETE DATA FILES
+
+If any of the recovery files or data files have the wrong filename, then
+par2cmdline will not automatically find and scan them.
+
+To have par2cmdline scan such files, you must include them on the command
+line when attempting to verify or repair.
+
+e.g.:
+
+  par2 r test.mpg.par2 other.mpg
+
+This tells par2cmdline to scan the file called other.mpg to see if it
+contains any data belonging to the original data files.
+
+If one of the extra files specified in this way is an exact match
+for a data file, then the repair process will rename the file so that
+it has the correct filename.
+
+Because par2cmdline is designed to be able to find good data within a
+damaged file, it can do the same with incomplete files downloaded from
+UseNet. If some of the articles for a file are missing, you should still
+download the file and save it to disk for par2cmdline to scan. If you
+do this then you may find that you can carry out a repair in a situation
+where you would not otherwise have sufficient recovery data.
+
+You can have par2cmdline scan all files that are in the current directory
+using a command such as:
+
+  par2 r test.mpg.par2 *
+
+WHAT TO DO WHEN YOU ARE TOLD YOU NEED MORE RECOVERY BLOCKS
+
+If par2cmdline determines that any of the data files are damaged or
+missing and finds that there is insufficient recovery data to effect
+a repair, you will be told that you need a certain number of recovery
+blocks. You can obtain these by downloading additional recovery files.
+
+In order to make things easy, par2 files have filenames that tell you
+exactly how many recovery blocks each one contains.
+
+Assuming that the following command was used to create recovery data:
+
+  par2 c -b1000 -r5 test.mpg
+
+Then the recovery files that are created would be called:
+
+  test.mpg.par2
+  test.mpg.vol00+01.par2
+  test.mpg.vol01+02.par2
+  test.mpg.vol03+04.par2
+  test.mpg.vol07+08.par2
+  test.mpg.vol15+16.par2
+  test.mpg.vol31+19.par2
+
+The first file in this list does not contain any recovery data, it only
+contains information to verify the data files.
+
+Each of the other files contains a different number of recovery blocks.
+The number after the '+' sign is the number of recovery blocks and the
+number preceding the '+' sign is the block number of the first recovery
+block in that file.
+
+If par2cmdline told you that you needed 10 recovery blocks, then you would
+need "test.mpg.vol01+02.par2" and "test.mpg.vol07+08.par". You might of course
+choose to fetch "test.mpg.vol15+16.par2" instead (in which case you would have
+an extra 6 recovery blocks which would not be used for the repair).
+
+REED SOLOMON CODING
+
+PAR2 uses Reed Solomon Coding to perform its calculations. For details of this
+coding technique try the following link:
+
+``A Tutorial on Reed-Solomon Coding for Fault-Tolerance in RAID-like Systems''
+<http://web.eecs.utk.edu/~plank/plank/papers/CS-96-332.html>