Quote:
Originally Posted by DiapDealer
Configure Sigil to automatically do it that way?
|
Yes, that's my wish.
Quote:
Originally Posted by DiapDealer
No. New ePubs will always have a unique ID automatically generated. A unique identifier is required by the ePub specs, afterall (required to BE there, there is no mechanism to enforce of the actual uniqueness of said identifier in ePub). And since Sigil won't yet know what the ISBN of your brand new ePub might be, it will generate a UUID to ensure compliance in the meantime.
|
I think of an option like:
[x] Delete UUID automatically, if an ISDN exist and use it as BookID
Of course I know how to delete it manually in the code.
My wish is, that Sigil supports the editor in producing OPFs which are as free as possible from superfluous code.
If developers are reading this thread: please just take my wish as a suggestion
Another option I'm looking for:
Change the pattern of the automatically generated IDs:
Now:
id="title.xhtml"
id="ch01.xhtml"
I prefer:
id="title"
id="ch01"
In other words: Just the filename as ID, without the extension.