View Single Post
Old 10-26-2016, 10:35 AM   #20
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,699
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Doitsu View Post
Sigil uses UUIDs as the dc identifier:

Code:
<dc:identifier opf:scheme="UUID" id="BookId">urn:uuid:8dd87b4e-79e5-4713-87e0-ae7525ab2887</dc:identifier>
If you're pre-pending it with an "s", it won't be flagged by epubcheck but it's technically no longer a valid 128-bit hex value.

Might I suggest that you simply replace the first character of the generated UUID with an a, b, c, d, e or f?
Good point about the dc id. We could easily replace the first character, I'm just not sure if doing so will still guarantee uniqueness 100% of the time.

My second suggestion may still work--depending on how/where the BookID is generated. Otherwise, it may come down to checking the first character and regenerating a uuid until one that starts with a valid character is generated. I'm not crazy about that idea.
DiapDealer is offline   Reply With Quote