Mobileread
Why ePub 3?
#1  JSWolf 09-17-2017, 02:09 PM
Why create an ePub 3 eBook that really uses none of the ePub 3 specific features? What good does that do? I can't think of any good. It would actually be easier to create ePub 2 eBooks unless you need some ePub 3 feature.
Reply 

#2  KevinH 09-17-2017, 03:25 PM
It can use more advanced semantic features that will help people with disadvantages. It can also hold audio and video legally (some epub2 try to extend with these). Furthermore, when properly created with guide and toc.ncx, then can easily be backwards compatible with epub2.

So the real question is why use still use "epub2" when you can create a fully backwards compatible "epub3" to support both markets and provide additional features if so desired and provide better semantic meaning support for disadvantaged readers.

Perhaps it is time to fully retire legacy "epub2" and work to make "epub4" something better for everyone.
Reply 

#3  DiapDealer 09-17-2017, 04:14 PM
Quote KevinH
So the real question is why use still use "epub2" when you can create a fully backwards compatible "epub3" to support both markets and provide additional features if so desired and provide better semantic meaning support for disadvantaged readers.
Exactly.
You're not "fighting the good fight" by clinging desperately to EPUB2 just because there's nothing in your book that would require EPUB3.
Reply 

#4  salamanderjuice 09-17-2017, 04:58 PM
Quote DiapDealer
Exactly.
You're not "fighting the good fight" by clinging desperately to EPUB2 just because there's nothing in your book that would require EPUB3.
Yep. It's just holding devices back. Epub 3 is 6 years old at this point and support is still lacking to non-existent in a lot of software and devices. That's kind of crap. I'm not expecting my eReader to handle video ever, but it's ridiculous that every reader can't handle RTL languages and vertical text at this point. Lack of MathML support is also seriously dampening the digital textbook market.

By clinging to epub 2 developers and manufactuers have no incentive to implement epub 3. Even if a lot of people will never notice or encounter an epub 3 feature it sucks for those that do need them.
Reply 

#5  JSWolf 09-17-2017, 05:07 PM
I'm not talking about extra features of ePub 3. I'm asking why make ePub 3 that doesn't use any ePub 3 only features. That doesn't need to be ePub 3. That's easier to make as ePub 2. What advantage does ePub 3 give in this circumstance?

The problem for ePub 3 is that most ePub reading software doesn't implement ePub 3 enough or hardly at all. Take all those old Sony Readers out there. They'll never support ePub 3. One of the real reasons that ePub 3 has not taken off is Adobe and their new DRM. That forces people to stick with ADE 2.0.1 which is not ePub compatible.
Reply 

#6  DiapDealer 09-17-2017, 06:05 PM
Quote JSWolf
I'm not talking about extra features of ePub 3. I'm asking why make ePub 3 that doesn't use any ePub 3 only features..
And we're asking "why not?" Every RMSDK-based reader out there can handle them. Why cling blindly to EPUB2 for no reason?
Reply 

#7  AnotherCat 09-17-2017, 07:03 PM
Quote JSWolf
Why create an ePub 3 eBook that really uses none of the ePub 3 specific features? What good does that do? I can't think of any good. It would actually be easier to create ePub 2 eBooks unless you need some ePub 3 feature.
I agree that is so and also add that it applies to the vast majority of books, eReaders and the needs of readers of the books too.

I am not sure the other respondents to your post are qualified to comment as they seem to not have the ability to understand and properly respond to your very specifically stated question . Perhaps they could start their own thread asking the unrelated question that they seem to want to ask here?
Reply 

#8  DiapDealer 09-17-2017, 07:28 PM
Quote AnotherCat
I agree that is so and also add that it applies to the vast majority of books, eReaders and the needs of readers of the books too.

I am not sure the other respondents to your post are qualified to comment as they seem to not have the ability to understand and properly respond to your very specifically stated question . Perhaps they could start their own thread asking the unrelated question that they seem to want to ask here?
Actually, no. I'm quite qualified. And I understand the question perfectly. It's just that the question is utterly pointless.

What Jon (and apparently others) fail to understand is that "why make epub3s?" is just as random and pointless as "why not make epub3s?" So the answer to his question "why" is quite simple. It's "why not?"

The fact of the matter is, epub2 is no longer defacto. The majority of commercial epubs I buy from the major vendors are epub3 already. The few that aren't, get converted. Mostly because I prefer the epub3 rendering engine in my reading software. My epub library is quickly becoming entirely epub3. The fact that none of them contain any "epub3 specific features" (whatever the heck that even means) is entirely irrelevant.

My *.doc files all eventually became *.docx, even though the vast majority of them could have happily lived out their lives as *.doc (containing no features that .docx would enhance). Why? Because things change. And because I can.
Reply 

#9  KevinH 09-17-2017, 10:46 PM
Couldn't agree more. The newer rendering engines are generally better. Epub3s are becoming more prevalent for commercial distribution. The epub3 format allows you to do more, if you so desire, or you can simply make things backwards compatible for older epub2 only readers.

That is why we added epub3 generation support to Sigil while having it keep the guide and toc/ncx for backwards compatibility reasons. Creating an epub3 can now be as easy as creating an epub2 with almost no downsides and the added benefit of allowing newer devices and rendering engines.
Reply 

#10  AnotherCat 09-17-2017, 11:15 PM
As I was reading your post I was thinking of asking you what the advantages of epub3 were for the vast majority of us until I got to -

Quote DiapDealer
...My epub library is quickly becoming entirely epub3. The fact that none of them contain any "epub3 specific features" (whatever the heck that even means) is entirely irrelevant...
At which point I fell off my chair laughing and choking on my coffee as your own words then make the case for the reasoning behind the original poster's question; a question you seem to have dismissed as not worth asking.
As an aside, using a .doc versus .docx comparison with epub2 vs epub3 is not a good one. While for your usage the advantages of .docx seem to be not apparent, for other than casual users of .docx the advantages are very much apparent and very useful.
Reply 

  Next »  Last »  (1/9)
Today's Posts | Search this Thread | Login | Register