Quote:
Originally Posted by DNSB
ePub3 has been my standard format for the last 7 years. I generally use Sigil's ePub3-itizer to handle much of the basic changes needed when I receive ePub2 books and then another of my collection of saved searches to give me a start on finishing the task.
I tend to use ePub3 with very few ePub3 extensions for books intended for others and to code to support both. I may change this in the near future since I no longer see any good reason for using strict ePub2 only syntax. Most renderers are capable of handling some of the simpler ePub3 extensions. Even Amazon's KDP has support for quite a bit of ePub3 now.
For myself, I will use quite a few of the advanced ePub3 (i.e. they make tasks much simpler/easier than ePub2) features and forget about backwards compatibility. Some types of book are much easier in ePub3 such as using fixed layout for early reader books (the ones that tend to have a lot of pictures with overlaid text). Others are more trivial such as wrapping text around an image with simple code that will work on Thorium & Kobo's kepub while the ePub2 code tends to be a lot iffier especially when the page resolution varies so you need media queries to handle them properly. Yes, I could still do this in ePub2 but ePub3 makes those tasks simpler.
Note that this is with my generally very boring book layout practices, other people whom I chat with and who prefer more complex layout needs switched to ePub3 fully long before I did.
|
When you edit ePub3, do you use webkit code?