View Single Post
Old 03-21-2025, 11:14 PM   #21
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,424
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Rather interesting result after deliberately introducing errors in the .opf file.

I added a space after the colon in the dc:language element and ran epubcheck expecting to get an error message. As soon as I clicked on epubcheck, the line changed. Pasted the modified line back and the same thing happens when I switch away from the .opf file for any reason.
Quote:
before:
<dc:identifier id="EbookISBN">9780391234567</dc:identifier>
<dc: language>en</dc:language>
<meta property="dcterms:modified">2025-03-21T00:16:26Z</meta>
<dc:date>2019-05-09</dc:date>
Quote:
after:
<dc:identifier id="EbookISBN">9780391234567</dc:identifier>
<dc:>en</dc:>
<meta property="dcterms:modified">2025-03-21T00:16:26Z</meta>
<dc:date>2019-05-09</dc:date>
I hadn't noticed this happening before but I haven't made a habit of deliberately introducing an error in the .opf file.
DNSB is offline   Reply With Quote