07-31-2013, 07:43 AM | #46 | |
Grand Sorcerer
Posts: 11,732
Karma: 128354696
Join Date: May 2009
Location: 26 kly from Sgr A*
Device: T100TA,PW2,PRS-T1,KT,FireHD 8.9,K2, PB360,BeBook One,Axim51v,TC1000
|
Quote:
It's not on Youtube and I'm pretty sure the clip on Hulu is not accessible everywhere. Try a web search for: shimmer floor wax saturday night live In the meantime, here's a transcript: http://snltranscripts.jt.org/75/75ishimmer.phtml What I'm saying is that it doesn't make sense to jam together specifications for two very different products into one. The result is going to be suboptimal for both. epub3 as published was a bad idea from the start. The reality we are seeing is that the epub3 stakeholders, the people whose livelihood depends in some measure on commercial ebooks not sold by Amazon, have found the existing epub3 specification too unwieldy to fully implement and have been implementing those features that make sense for *their* customers. If MathML isn't in there, well, that tells you what *they* think of it. It doesn't make sense to *them*. What any specific customer needs or wishes to see isn't really factoring into it; if you look at the list of stakeholders listed by the AAP, they don't see readers or writers as stakeholders, only the middlemen. epub3lite (or whatever they call it in the end) is an attempt to coordinate so that all the stakeholders doing partial epub3 implementations support the same sub-set the same way and deprecate the same features. They need a spec that will let them go make money (like Amazon and Apple are) instead of waiting for a gold-plated religious symbol of standardization to magically appear. The full spec has been out for two years without being implemented, and the AAP crowd obviously think it won't be implemented within the next year if they don't trim out the bloat and get *something* out there. Especially since that is what proprietary format vendors like Apple and Amazon did to create *their* rich content ebook formats in a timely fashion. Amazon got the job done in six months so, unless their software developers are way better than everybody else's, the failure of epub3 to materialize lies in the spec's attempt to be everything to all people and feature triage is the only option left to them. In the tech world, decades of product design successes and failures have shown that letting marketting types write the specs for products leads to failure every time. That is why the techie mantra is K.I.S.S. - "Keep it Simple, Stupid". The proper, time-proven solution isn't kitchen sink specs; it is market segmentation. Different products, each optimized for its intended mission and audience. Textbooks and technical papers *are* different from narrative text and cookbooks. Two different products selling at vastly different prices to very different buyers. So why commingle the two? Might as well try to sell a floor wax that is also a desert topping. |
|
07-31-2013, 08:39 AM | #47 |
Wizard
Posts: 1,234
Karma: 3350652
Join Date: Feb 2008
Device: Amazon Kindle Paperwhite (300ppi), Samsung Galaxy Book 12
|
Because of course, if there isn't time and money to do it right the first time, there's always a way found to do it over after everyone is exhausted by yelling about the errors.
And, those superscripts directly set in ePubLite will be properly handled by a screen reader, right? Last edited by WillAdams; 07-31-2013 at 11:51 AM. |
Advert | |
|
07-31-2013, 02:26 PM | #48 |
affordable chipmunk
Posts: 1,290
Karma: 9863855
Join Date: Feb 2011
Location: Brazil
Device: Sony XPeria ZL, Kindle Paperwhite
|
I don't get it. isn't epub simply zipped html and css?
|
07-31-2013, 02:39 PM | #49 | ||
Grand Master of Flowers
Posts: 2,201
Karma: 8389072
Join Date: Oct 2010
Location: Naptown
Device: Kindle PW, Kindle 3 (aka Keyboard), iPhone, iPad 3 (not for reading)
|
Quote:
I think the biggest problem with the EPUB 3 standard is that it was drawn up by a committee. Design by committee often leads to bloat because there is no one to say "no". There is no product designer to make the hard decisions about what the design needs, what would be nice to have but might not be technically feasible, and what the design doesn't need. Quote:
|
||
07-31-2013, 02:42 PM | #50 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
One could simplistically think of it as being so, but an ePub document can contain rather more than that, such as SVG images, video, and audio content, too, as well as XML files which tie it all together.
|
Advert | |
|
08-02-2013, 10:21 PM | #51 |
ePub Maker
Posts: 120
Karma: 16
Join Date: Dec 2009
Location: Mordor
Device: iPad,Kindle 3, Nook 2
|
We can invent another format easily, which supports everything in the file, such as you can embed PDF, Word, and everything you need.
But without reality support and implementation, what the meaning of it? |
08-03-2013, 12:41 AM | #52 | |
Nameless Being
|
Quote:
A company, like Amazon, can decide that product X is going to include the feature set Y. Feature set Y was decided upon because they want to reach the set of markets represented by Z. Employees must then implement X. The success of that product is determined based upon how Y represents the needs of Z and how much access the company has to Z. When it comes down to committees, you have to decide what Z is. Since different companies serve different markets, that is a complex task. Once that is done, the members have to decide upon Y. Since each company is serving a different Z they will each see market needs differently, thus have different perspectives on necessary feature sets, which makes deciding upon Y difficult. Finally, X is no longer a singular item. It is now a set of products (call it XS). Since different developers have different approaches to implementing Y, the elements in XS have slight incompatibilities that take time to sort out. Now if that description didn't leave your head spinning I didn't do my job because standards by committee seem to be written in a somewhat more obtuse language to avoid a lot of ambiguity because it has to go through multiple hands and the details need to be implemented in similar ways in order for things to work. It isn't like internal company documentation that can be sketchy at points because the authoritative reference is the reference implementation, i.e. the product, which is easy to modify before the product is released (and sometimes even after the product is released). |
|
08-03-2013, 04:01 AM | #53 |
Uebermensch
Posts: 2,583
Karma: 1094606
Join Date: Jul 2003
Location: Italy
Device: Kindle
|
My thoughts exactly when I first heard about ePub. It seems like there is an aweful amount of time spent on schemantics whereas really the main content is just XHTML 1.1.
If you take a closer look you'll see there is more about it. First, ePub has to be supported by a wide range of hardware. That includes old E Ink devices with limited memory and slow CPU. You need to do something about the XHTML file and included static material so that it won't overflow your device's memory. Second, there is the question how to include and present various metadata, how to include inline images, support DRM (some people ask for it...), extend functionality through XML, and support audio/video content. |
08-03-2013, 06:16 AM | #54 |
Grand Sorcerer
Posts: 6,111
Karma: 34000001
Join Date: Mar 2008
Device: KPW1, KA1
|
EPUB, SchmEPUB. Blablablabla.
One of the things I hate most in IT or computer-related stuff. Nobody can ever agree, because there's a zillion way of doing things. In the end, we just have a zillion different systems, of which only very few people have any real in-depth knowledge. Then, just before one of those systems can actually become THE real standard, one or another thinks it should be done in yet another way, and it starts all over again. As I've said in other posts, I'm re-ripping my CD's into FLAC. Some people have asked me why I don't use ALAC or APE or whatever. Why? Easy. FLAC is free, it's not covered by patents, it has been stable since 2007 (now in 2013, an update has been released to make it easier to compile, using newer compilers), it's crossplatform running basically everywhere, it can be used from the command line or through a GUI, it has good compression, it's supported by quite a lot of hardware, most audio-related software, and it's the default standard to sell lossless music. Why the hell do we *NEED* anyhting else? FLAC does everything already. Other standards improve only some very infinitesimally small points, while having some great disadvantages to offset those. For digital music, this is what counts: Uncompressed: WAV (AIFF for Apple) Lossless compression: FLAC (ALAC for Apple stuff) Lossy compression: MP3, Ogg Vorbis for the open-source minded (AAC for Apple stuff) If you discount Apple, who is almost always different because of just wanting to be different (which is the reason why I avoid buying stuff from them), the only relevant formats are WAV, FLAC, MP3 and Ogg Vorbis. All of the rest is just dabbling in the margins, IMHO. I am of the opinion that it's the same with EPUB. Compared to AZW and EPUB (and iBooks...) everything else is irrelevant. Instead of screaming for new standards al the time, I think the book industry should follow the music industry's example, and develop EPUB into a solid, stable standard (and ditch the DRM). Last edited by Katsunami; 08-04-2013 at 06:37 PM. |
08-03-2013, 06:55 AM | #55 |
Wizard
Posts: 4,812
Karma: 26912940
Join Date: Apr 2010
Device: sony PRS-T1 and T3, Kobo Mini and Aura HD, Tablet
|
I'm of two minds.
Epub as it was 3 years ago seemed to be fine on my old Sony reader. KISS If nobody tried to make things better we would be still crossing the country in covered wagons with wooden wheels or living in caves. Helen |
08-03-2013, 08:49 AM | #56 |
Grand Sorcerer
Posts: 6,111
Karma: 34000001
Join Date: Mar 2008
Device: KPW1, KA1
|
You are right, but there is a difference in making things better, as opposed to just doing things differently.
Also, I am of the opinion that it is ridiculous to try to have one big giant format for every device. There is nothing wrong with using a perfected version of the current EPUB standard for e-readers only, and develop add-ons to that standard, to be used on tablets and other devices, as is necessary. |
08-03-2013, 09:02 AM | #57 | |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
Quote:
|
|
08-03-2013, 10:34 AM | #58 |
Grand Sorcerer
Posts: 6,111
Karma: 34000001
Join Date: Mar 2008
Device: KPW1, KA1
|
Then add those features as options or modules or whatever. IMHO, it's still not necessary to start another all-but-the-kitchen-sink standard from scratch again.
|
08-03-2013, 11:26 AM | #59 |
Grand Sorcerer
Posts: 11,732
Karma: 128354696
Join Date: May 2009
Location: 26 kly from Sgr A*
Device: T100TA,PW2,PRS-T1,KT,FireHD 8.9,K2, PB360,BeBook One,Axim51v,TC1000
|
Most ebook readers support multiple formats already.
The best do it seamlessly so that the user doesn't need to know what is in the file, just that it is an ebook and it works with their readers. That is how Nook does it with graphic novels and magazines and how Amazon does it for everything: we techies know that Kindle files can be Topaz, Mobi7, Fixed-Format (pdf), KF8, even audible. Kindle is a brand, not a spec. All that regular consumers need to know if that it is an ebook that works with Kindle readers and apps. Ditto for Nook. And to an extent Sony and Kobo. |
08-03-2013, 11:40 AM | #60 | |
Grand Sorcerer
Posts: 11,732
Karma: 128354696
Join Date: May 2009
Location: 26 kly from Sgr A*
Device: T100TA,PW2,PRS-T1,KT,FireHD 8.9,K2, PB360,BeBook One,Axim51v,TC1000
|
Quote:
When bugs are found in features that don't impact their customers, some players will be inclined to ignore the fixes so that over time there is drift in the implemented products and people who expect that any product supporting the spec will offer the same experience run into all sorts of "minor" inconsitencies and incompatibilities. Grumbling ensues. Everybody loses. This has happened before (SGML, for one); it likely will happen again, even though you'd think the committee standards crowd would get the message. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PDF is dead.... Long live PDF | Justin Nemo | Writers' Corner | 50 | 04-07-2012 06:25 AM |
The Magazine is Dead. Long Live the Magazine! | kennyc | News | 17 | 11-01-2010 12:36 PM |
The PRS-500 is dead, long live the PRS-600... | AprilHare | Lounge | 18 | 05-11-2010 06:48 PM |
My 505 is Dead, Long Live the 505 | megasad | Sony Reader | 11 | 10-22-2009 04:21 AM |
The eSlick is dead. Long live the eSlick. | lance_ | Lounge | 10 | 09-02-2009 03:46 PM |