Quote:
Originally Posted by carmenchu
Do you mean the complaint
'Non-standard image resource of type image/webp found'?
I get as meaningful complaints about this line:
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">,
appearing in lots of epubs from lots of sources... left bothering about it: as a reader, it means nothing. Far worse:
- typos galore (but for hut and the like)
- semantics absent (that may be the author: but editors ought to do something, especially when promoting a 'new author'...)
- unfriendly formating
- nonsensical translations...
Anyway, mine is sctrictly a personal viewpoint: I love the books in the my library and I love to give them the best layout I can contrive. No 'use and discard' for me.
|
The error for the <html> tag is fairly common. And relatively harmless though adding lang="xx" to the <html> tag is not supported in epub2. One of my saved searches cleans that up. It won't keep your ebook from displaying on any platform that I am aware of.
Typos? Semantics? Homonyms? Formatting? The epub specifications don't care about what you do with your text. It's your ebook. Screw up the content to your heart's content. Hmmm... that's pretty much what ScrambleEbook and Borkify do.
Ebooks in my library? They get the formatting I prefer. Save a few bytes so I can't read them on my devices? No futtering way.
Ebooks I work on for other people? They will pass epubcheck. They will have formatting that looks good across multiple devices and reading platforms. On request, I may even do a quick read and correct any egregious errors.
You might also want to look at
Usage statistics of WebP for websites. Other sites have similar statistics with the highest claiming 0.4% of websites using webp images on their survey of the "top" 500 sites. If you drop Google, the number went to 0.2%.