Quote:
Originally Posted by KevinH
Interesting article. Yes a new standard would be a big improvement. Trying to shoehorn it into epub3 would not.
|
That's highly debatable. If a new standard is made by someone else than the people that gave us EPUB, maybe. Otherwise it will just be the same old mess hiding behind a new name.
Quote:
|
That said, Thorium will not work with pure html5 directly (I tested it) but it sounds like they are working on it.
|
They appear to be doing some weird self contradictory things. First they say that the XML serialization of HTML 5 is fine and works in thorium. Then they go on to say that if an ebook has the non XML serialization for HTML 5 they will disable features such as pagination in their reader. I dont follow why the serialization format should make any difference to what features reader software supports. The actual DOM that is being serialized is independent of the format chosen for serialization and ebook reader features should depend on the DOM + CSS + JS not the serialization.
All-in-all it looks like there is a ton of confusion in this space. Starting with the people proposing this change who dont seem to understand that the serialization of HTML is irrelevant to what features it supports.
Like I said in my previous post the *only* pro for non XML serialization is that it is easier to author using a plain text editor.