MobileRead Forums - View Single Post

DiapDealer · 09-20-2017, 07:49 AM

The id attribute is required for the navPoint element. And yes, it must he unique. But it also has to conform to xml standards which require that ids do not start with a digit. The one you're dealing with was auto-generated (a urn guaranteed to be unique) by a program when building the toc. Unfortunately, those generated, unique urns sometimes start with number. I honestly don't know that they are "used" per se.

Sigil used to be susceptible to generating invalid ids like that, but that bug was fixed a while back. At least I think it was. At the time, the bugfix was about opf manifest ids rather than toc ids, but I assume the fix was applied to a general id-generating utility function.

09-20-2017, 07:49 AM	#2
DiapDealer Grand Sorcerer Posts: 28,614 Karma: 204624552 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	The id attribute is required for the navPoint element. And yes, it must he unique. But it also has to conform to xml standards which require that ids do not start with a digit. The one you're dealing with was auto-generated (a urn guaranteed to be unique) by a program when building the toc. Unfortunately, those generated, unique urns sometimes start with number. I honestly don't know that they are "used" per se. Sigil used to be susceptible to generating invalid ids like that, but that bug was fixed a while back. At least I think it was. At the time, the bugfix was about opf manifest ids rather than toc ids, but I assume the fix was applied to a general id-generating utility function. Last edited by DiapDealer; 09-20-2017 at 08:03 AM.