Manifest ID filename unchanged

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?

Turtle91 · 12-21-2024, 09:52 AM

As far as I understand, those IDs in the OPF are fairly recent and, by design, don't need to change. The user will never see the IDs in the OPF, they will only ever see what you put at the top of each html page in the <title> tag...and then there are some devices/apps that don't even show those. The filename that you are changing in the Book Browser pane is really for organizational purposes...and the ID in the OPF is so that you can have duplicate filenames without causing the ePub to implode.

KevinH · 12-21-2024, 10:05 AM

No. It is not a bug. I will check to see if the manual needs to be updated but that only happens once every couple of Sigil releases, as getting volunteers to help update our user guide is next to impossible.

There is no requirement to base manifest ids on filenames at all. The only spec is that the manifest id be unique. Some epub publishers use uuids here for that reason.

In order to support mass renaming of thousands of files, and because the approach used to rename ids in older versions of Sigil only worked for epub2 (it was broken in epub3 and could introduce subtle errors), Sigil decided to stop changing still unique manifest ids when renaming files. This happened quite a while back.

For those people who insist to create unique manifest ids from current filenames, we recently added in a new tool to rebase all ids on current filenames if the user so chooses. It properly handles both epub2 and the more complex epub3 correctly.

I am thinking about creating a tool that will assign uuids instead.

And finally you control the default naming scheme for new files, and can set a template file that loads the template/blank epub you specify.

12-21-2024, 09:44 AM	#1
philja Addict Posts: 265 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?

12-21-2024, 10:05 AM	#3
KevinH Sigil Developer Posts: 8,759 Karma: 5706256 Join Date: Nov 2009 Device: many	No. It is not a bug. I will check to see if the manual needs to be updated but that only happens once every couple of Sigil releases, as getting volunteers to help update our user guide is next to impossible. There is no requirement to base manifest ids on filenames at all. The only spec is that the manifest id be unique. Some epub publishers use uuids here for that reason. In order to support mass renaming of thousands of files, and because the approach used to rename ids in older versions of Sigil only worked for epub2 (it was broken in epub3 and could introduce subtle errors), Sigil decided to stop changing still unique manifest ids when renaming files. This happened quite a while back. For those people who insist to create unique manifest ids from current filenames, we recently added in a new tool to rebase all ids on current filenames if the user so chooses. It properly handles both epub2 and the more complex epub3 correctly. I am thinking about creating a tool that will assign uuids instead. And finally you control the default naming scheme for new files, and can set a template file that loads the template/blank epub you specify. Last edited by KevinH; 12-21-2024 at 10:39 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Save/Export Books Unchanged	sempiter	Library Management	7	04-09-2021 05:44 AM
[Possible Bug] Unchanged Modification Date after Sigil edit	recook	Calibre	8	03-03-2021 10:13 AM
Kindle Hardware Basically Unchanged?	Forbid	Amazon Kindle	6	11-23-2020 07:29 PM
Epub to KF8, unchanged?	Barb-B	Conversion	5	03-28-2013 05:39 PM
iTouch - sync appears to work, but content unchanged	HomeInMyShoes	Apple Devices	2	10-07-2011 02:28 PM

12-21-2024, 09:52 AM	#2
Turtle91 A Hairy Wizard Posts: 3,347 Karma: 20171571 Join Date: Dec 2012 Location: Charleston, SC today Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire	As far as I understand, those IDs in the OPF are fairly recent and, by design, don't need to change. The user will never see the IDs in the OPF, they will only ever see what you put at the top of each html page in the <title> tag...and then there are some devices/apps that don't even show those. The filename that you are changing in the Book Browser pane is really for organizational purposes...and the ID in the OPF is so that you can have duplicate filenames without causing the ePub to implode.

Advert