Does it go faultless. That would be nice, but far from reality. There are many sources of errors. The source material you receive is not always free from errors. There can be errors in the structure of the folders and last but not least this author have at least not tested everything and is using utilities from other developers, which have unintended left some bugs behind.
Errors in source material.
A CBook is a compressed folder structure with images (CBR and CBZ files) or a compiled mixture of all kind of objects, such as text, images, movies, and others (PDF). The sources of error are corruption in the images, structure of the folder(s), unknown objects, and incomplete or corrupt compression. The package tries to extract images using the mentioned tools and own code to perform this task. Any deviation from what is expected during this process is reported and put in a special error report in the folder of the CBooks.
The user can choose to have summarized report or extensive reporting.
The report hereafter gives an example of a summary report.
This report only shows that it is serious and that the CBook is probably unusable.
In case you want to receive a detailed report enable 'Extensive error reporting'.
Each future report contains all the information it received during the creating of the image and menus.
Use the RESET command to recreate the error reports. The files are retested and when errors are found (very likely) they will be reported now in an extensive report.
In the above report we can see that the during the extraction of a CBR file one of the images is corrupt and the rest of the images are missing. The file is truncated either during the upload or download. Further it tells that the error is too serious to add it to the menu. The corrupted file is renamed with the extension .err.
The command Error reports creates an overview of the all error reports in your library.