[KevinH]

Some addition thoughts/questions for those following along:

1. Since some people place the loi immediately after the toc near the front of the book and some want it at the end (standardebooks), I am just going to append the loi.xhtml file to the end of the spine if a new one is needed. The user can drag and drop it to wherever they want it after the plugin completes.

2. Updating the ncx or nav toc will depend on final position of loi in the spine depending on the user's choice. So users will have to remember to regenerate the nav/ncx table of contents so they will match after running this plugin.

3. The plugin will add the "loi" semantics on the new file to the opf guide for epub2 and nav landmarks for epub3 so that repeat use without constant new files is possible.

4. I am think of looking for user created loi_template_2.xhtml and loi_template_3.xhtml in the sigil preferences folder for use when having to create a new loi.xhtml file.
That way users can customize those files and use a properly translated heading for "List of Illustrations" for their chosen language.

5. Instead of generating a log file of the images found that were *not* considered suitable for the loi, perhaps we should simply add them to the loi.xhtml in the proper found order but wrap each one in xhtml comments to hide them from the reader.

That way anyone can edit the newly created file and uncomment any mistakes easily or use it as a list of potential images to fix. (or to quickly link to each to visually check things out).
This could be controlled by a plugin preference setting.

Thoughts on any or all of this welcomed.