Quote:
Originally Posted by KevinH
An "i" tag is valid html5 and therefore valid for epub3. It even has a slightly different semantic than the "em" tag. A forign word, a ship name, etc vs just "emphasis". How on earth can Google Play Publish make such a rule. It is not part of the epub3 spec. Itunes ibooks does allow the use of both the "i" tag and the "em" tag. Sounds like the "thought police" are back in action and this time are reading your mind to determine that the "i" tag is somehow inappropriate.
I would file a bug report with Google Play publish and tell them they are neither the owner of the epub3 spec nor can they read minds to determine how the author meant to use "i" vs "em".
So silly.
|
Indeed it is silly. Sadly, it just kept spitting up errors (along with Itunesconnect) when I used the <i> tag. I'm not convinced that such a request would be high in their current list of priorities though. Same with Apple.
Apple's own documentation points to this web page:
https://www.w3.org/TR/html401/struct/text.html and it was from here I got the idea for using <em> instead (and that just works).