MobileRead Forums - View Single Post - What Features or Tools does Sigil Still Need Yet?

KevinH · 02-09-2021, 04:17 PM

Thanks BeckyEbook. But those calibre links appear to be for kfx and mobi ebooks and not epubs that are conversions from mobi.

If you have a mobi book with an asin in calibre and convert it to epub3, what metadata will it produce in the newly converted epub3 opf related to the asin?

In epub3 under the epub3.2 spec, the dc:identifier is not allowed the scheme attribute and so the scheme info is typically kept in the content field by adding a urn:XXXX: preface (similar to what DNSB's post showed first) or added by the use of identifier-type property is a separate refinement.

I will use calibre and Doitsu's approach for epub2, but I am just not sure exactly what calibre uses when it generates an epub3 from a mobi (or updates an epub2 to epub3) that has an asin as a dc:identifier?

02-09-2021, 04:17 PM	#153
KevinH Sigil Developer Posts: 9,268 Karma: 6565382 Join Date: Nov 2009 Device: many	Thanks BeckyEbook. But those calibre links appear to be for kfx and mobi ebooks and not epubs that are conversions from mobi. If you have a mobi book with an asin in calibre and convert it to epub3, what metadata will it produce in the newly converted epub3 opf related to the asin? In epub3 under the epub3.2 spec, the dc:identifier is not allowed the scheme attribute and so the scheme info is typically kept in the content field by adding a urn:XXXX: preface (similar to what DNSB's post showed first) or added by the use of identifier-type property is a separate refinement. I will use calibre and Doitsu's approach for epub2, but I am just not sure exactly what calibre uses when it generates an epub3 from a mobi (or updates an epub2 to epub3) that has an asin as a dc:identifier?