View Single Post
Old 10-05-2021, 08:24 PM   #2
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
None of those look to be valid ways of defining the ISBN in the OPF. At least, they are not how calibre does them. Personally, I don't care about the ISBN on the device, as there is no use for it there, so I haven't checked it for a while (and honestly, other than an identifier to help get metadata, it's pretty useless). But, testing it now, what calibre puts in works.

For epub 2, this is:

Code:
<dc:identifier id="isbn" opf:scheme="isbn">9781780891231</dc:identifier>
That does have the "unique-identifier" set to "isbn" in the package, but, that is not necessary.

For epub 3, it is:

Code:
<dc:identifier>isbn:9780515135282</dc:identifier>
The device read both of those as the ISBN and displays them in the details.

And the above works fro sideloaded kepubs as well.
davidfor is offline   Reply With Quote