Re-generating the toc is simpler, but if you have a special uuid, you can edit it manually. (You can edit the opf and the tox.ncx files with a text editor, or in the Sigil code window, but be very cautious)
I use Sigil, and I happen to create my own uuid manually, but even if I use the one generated automatically by Sigil, it will show in the content.opf as <dc:identifier blah blah ...
So the entry in the opf file looks like:
Quote:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<package xmlns="http://www.idpf.org/2007/opf" unique-identifier="BookId" version="2.0">
<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns pf="http://www.idpf.org/2007/opf">
<dc:identifier id="BookId" opf:scheme="UUID">urn:uuid:ecm-ABP-ST-24-07-2016</dc:identifier>
|
In the toc.ncx, the <meta content tag must match the opf file, thus
Quote:
<meta content="urn:uuid:ecm-ABP-ST-24-07-2016" name="dtb:uid"/>
<meta content="3" name="dtb:depth"/>
<meta content="0" name="dtb:totalPageCount"/>
<meta content="0" name="dtb:maxPageNumber"/>
|
The problem with a mis-matched uuid is that saving the epub in that condition will result in Sigil trying to "repair" the OPF file and you end with rather complex "nested" metadata tags.