MobileRead Forums - View Single Post

philja · 12-21-2024, 09:44 AM

In Windows Sigil 2.3.1 while building an epub3 from scratch, Sigil's starter epub3 has one text file named Section0001.xhtml which I renamed to Chapter1.xhtml. As I added further files, I systematically renamed each one in sequence, Chapterxx.xhtml.

Later when I looked in the content.opf manifest, I found that the first text file had retained its original name, Section0001.xhtml for its id.

I know there is a tool to "Rebase OPF Manifest IDs on Current Filenames" so it is not a problem for me, but from relevant text in the Sigil User Guide (2.3.0 and later), I got the impression that this behaviour was only in older versions of Sigil. So I wonder if this is a bug?

12-21-2024, 09:44 AM	#1
philja Addict Posts: 270 Karma: 516 Join Date: Nov 2015 Location: Europe EEC Device: Kindle Fire HD6 & HD8	Manifest ID filename unchanged In Windows Sigil 2.3.1 while building an epub3 from scratch, Sigil's starter epub3 has one text file named Section0001.xhtml which I renamed to Chapter1.xhtml. As I added further files, I systematically renamed each one in sequence, Chapterxx.xhtml. Later when I looked in the content.opf manifest, I found that the first text file had retained its original name, Section0001.xhtml for its id. I know there is a tool to "Rebase OPF Manifest IDs on Current Filenames" so it is not a problem for me, but from relevant text in the Sigil User Guide (2.3.0 and later), I got the impression that this behaviour was only in older versions of Sigil. So I wonder if this is a bug?