03-31-2014, 05:34 PM | #16 | |
Grand Sorcerer
Posts: 27,724
Karma: 197390418
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
They simply have no dog in the epub-spec-compliance hunt in my opinion. That's all on Kobo/Nook/iBooks/Sony/Adobe/etc's heads. |
|
04-01-2014, 08:56 AM | #17 |
Color me gone
Posts: 2,089
Karma: 1445295
Join Date: Apr 2008
Location: Central Oregon Coast
Device: PRS-300
|
No judgement implied, just a long sigh.
|
04-01-2014, 09:00 PM | #18 | |
Curmudgeon
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
|
Quote:
|
|
04-02-2014, 01:02 PM | #19 | |
Grand Sorcerer
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Quote:
Having said that Amazon is also tinkering with some sort of JSON standard as well for iOS version of its reader. Dale |
|
04-02-2014, 02:44 PM | #20 |
Grand Sorcerer
Posts: 27,724
Karma: 197390418
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
We'll have to agree to disagree then.
I've never been fully onboard with the "KF8 is just a compiled ePub" oversimplification. In a very loose, layman's overview ... perhaps. But that's beside the point. The truth is: the IDPF could disband tomorrow and Amazon would just take on the responsibility of publishing their own kindlebook source code specifications. After all ... a KF8 ebook can still be made from nothing other than a single html file. That's why the "executable written in 'C' has no stake in the 'C' standard" allegory isn't all that apt. You don't need an epub to create a KF8. The InDesign plugin renders InDesign documents into kindlebook source code. Sure, they have an interest in ePub specifications, but they don't really care if there's ever any overwhelming compliance in how all those epub specs are interpreted by developers creating epub rendering engines. Why would they? So yes ... they have a stake in the specs themselves I suppose. Just no stake (or interest) in how those specs are interpreted (complied with). Their ebooks will never be read by all those devices/apps that can't agree on how the epub specs should be interpreted. Last edited by DiapDealer; 04-02-2014 at 02:54 PM. |
Tags |
fragment, identifier, ncx, toc |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Fragment Identifier missing, but looks OK | flypig | ePub | 8 | 12-19-2018 06:58 PM |
FRAGMENT ERROR MESSAGE | dgbeig | ePub | 5 | 11-23-2013 07:21 PM |
Bulk edit of identifiers | rmagere | Library Management | 4 | 02-19-2012 04:10 AM |
Search on Identifiers Field | nynaevelan | Library Management | 2 | 01-25-2012 06:13 PM |
Modifying Identifiers | Fabe | Sigil | 6 | 01-11-2012 07:46 AM |