01-20-2013, 07:17 PM | #31 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Hitch |
|
01-20-2013, 07:22 PM | #32 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
I was absolutely charmed after my discussion with her, naturally. I'd also add that given what Createspace and other POD companies will offer, in terms of print design, for under $300, those InDesigners are going to be finding other venues for earning, anyway (probably designing marketing materials, which, I'm told, still pays.) Don't misunderstand me: unlike lots of geeks, I don't hate InDesign; but there's no reason to use it for ebook layout. I know Liz loves it, but...I think that's simply a matter of being comfortable with what she knows, rather than seeing it as a masterpiece of ePUB-making software. Hitch |
|
01-20-2013, 07:28 PM | #33 |
Wizard
Posts: 1,496
Karma: 11250344
Join Date: Aug 2010
Location: NE Oregon
Device: Kobo Sage, Forma, Kindle Oasis 2, Sony PRS-T2
|
In general, I've found that if an epub looks OK in ADE, it will display quite decently on my Sony readers (350, 950, T1). It will also usually display passably well in these Android apps: Mantano, Aldiko, Bluefire, Sony, Nook, Overdrive. The Kobo app tends to add margin to that which is already in the epub, so it's not quite as good on display as the others. Mind you, all I've tested are fairly basic, mostly text epubs.
The exception was when I put an epub with a couple large images on the Sony, i.e. 1500px wide high quality JPEG and a 1500px wide PNG (small in file size) and they came up as blank pages. Display was fine in ADE. Reducing to 1200px wide solved the issue. So the Sony readers may have some limitations on image size. If you get into the apps that offer a lot of customization options like FBReader and CoolReader and Moon+, those may not display your book quite like you styled it. The goal for me personally is to just be sure my epubs are readable in those apps. I also test Kindle .mobi and .azw3 conversions. There are times when valid, working CSS does not translate in a conversion. I had KindleGen barf on some simple shorthand CSS once. It would sure be nice if every epub reader app or device could be consistent in display, but that's not real world right now. I think I even found one reader, a cloud reader called Fabrik that didn't display images. So test, test, test as best you can and realize there are going to be compromises, because you can't control what your reader will use to read with. |
01-20-2013, 09:29 PM | #34 | |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
Quote:
|
|
01-20-2013, 09:37 PM | #35 |
Resident Curmudgeon
Posts: 73,970
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
The problem with ePub 3 is all the multimedia stuff that has been added in. A lot of ePub is read on eInk which a lot of eInk readers won't handle well. What would have been better is the multimedia not added in and the other improvements kept. Then it would be a lot easier to upgrade. But until Adobe upgrades and most of the Readers get upgraded, it's not going to fly.
|
01-20-2013, 09:51 PM | #36 |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
Does anyone maintain a list of compatible code, likely to work on most epub readers and to survive Kindle conversion? If not, I'm tempted to start one.
I suppose I'll get lambasted for giving away Guild secrets :-) |
01-21-2013, 11:07 AM | #37 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
I know that there are 2-3 reading apps, all i-based, that have multimedia (and of course, PC and Mac-based readers), but until the devices go to it, I'm sticking with 2. And as far as the "new" TOC for all of them? I suspect of all the ePUB3 features, that and slightly more advanced CSS will be implemented before multimedia, due to the overwhelming number of e-ink devices that simply can't support video and/or audio. Hitch |
|
01-21-2013, 11:21 AM | #38 |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
Isn't it EASIER to make an ePUB3 book? Less worrying over what code you CAN'T use?
|
01-21-2013, 11:29 AM | #39 |
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
Once you decide that you'll do an EPUB3 book anyway and don't care about whether or not it will actually be supported... then, it's easier. But if you are not going to care about that, you could do an EPUB2 as well, and that's even easier because you just have to use Sigil
|
01-21-2013, 11:35 AM | #40 |
Grand Sorcerer
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Probably easier in theory, based on the spec. But then in practice, we'll be right back to figuring out what works and what doesn't in all the various vendor's implementations of that spec. You know... which portions they want to ignore, and what proprietary extensions they want to add. In practice, I look for ePub 3's implementation to be even more fragmented.
|
01-21-2013, 11:37 AM | #41 | |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
Quote:
|
|
01-21-2013, 12:00 PM | #42 |
frumious Bandersnatch
Posts: 7,516
Karma: 18512745
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
|
|
01-21-2013, 02:32 PM | #43 |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
I think the breakthrough in Sigil usage comes when you realise that Page View is mainly for checking you got what you entered in Code View right!
|
01-21-2013, 03:42 PM | #44 |
Guru
Posts: 644
Karma: 1242364
Join Date: May 2009
Location: The Right Coast
Device: PC (Calibre), Nexus 7 2013 (Moon+ Pro), HTC HD2/Leo (Freda)
|
Only if you're a coder. Us dabblers are using it in the opposite manner.
|
01-21-2013, 05:48 PM | #45 | |
Guru
Posts: 878
Karma: 2457540
Join Date: Nov 2011
Device: none
|
Quote:
I was going to suggest a workflow - prepare text in Indesign using very basic epub-compatible layout, leave it like that until ALL text revisions have been made. Then export an epub, continue tarting up in InDesign for the printed version. But that's too organized. Authors can't seperate content from layout. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Classic Nook Not Recognizing SD Card? | anamardoll | Barnes & Noble NOOK | 10 | 07-26-2011 12:16 AM |
new kobo - calibre not recognizing it | cybmole | Kobo Reader | 1 | 03-19-2011 01:09 PM |
azw to mobi: Not detecting chapters/page break at chapters and no TOC | RachDvn | Calibre | 3 | 01-16-2011 09:53 AM |
KOBO not recognizing chapters | Mostly Math | Kobo Reader | 2 | 06-13-2010 01:54 PM |
ePub Chapters vs. Stanza Chapters | kjk | Sigil | 4 | 09-14-2009 10:50 AM |