I got some words of advice from someone at Apple who works in iBooks Engineering a couple of years ago. Please encourage them to support HTML5/EPUB3 too while you are at it. Engineers are people too.Īnd of course none of this works on Kindle. If you have a sample that fails - post it in the forums, file a bug, help encourage them to take a look. We have had better luck with iBooks on Mavericks so we *think* we are doing the right thing and we *think* Edge is doing the right thing.but iOS/iBooks is having problems. It would be nice if Apple would be a bit more open about what is happening behind the scenes but they don't so we are left wondering.
We already have a wide range of behaviors and bugs with just EPUB2 readers, why would we not expect the same for EPUB3? So the idea that there are bugs and issues does not surprise me in the least. I have had conversations with folks we have created epub readers based on modern browsers and this is not a trivial thing. When we pass through Edge Animate we stick it in an and the implementation of which has its own sets of challenges. There really are a lot of moving parts which are only partially under the control of the InDesign team, the iBooks team and the Webkit team and everything has to fit together to work. Ha! You forget the power of engineering bugs and business realities which, IMHO, are often more powerful than evil intent.Īsk yourself, is the InDesign team more or less annoyed than you are with Apple? We wrote all this code, we wanted it to work, it didn't work. If Adobe don't make the next move in this horrid game with Apple, others will soon fill the void for interactive EPUB3 programs, such as PubCoder, BookCreator () and Aquafadas.Īdobe, any comments appreciated, even if they are to correct my assumptions.
Meanwhile, if Adobe can't find a way around this, they shouldn't advertise or build an expectation that Edge Animate output can be used in iBooks. So copying those files into the EPUB folder probably wouldn't have overcome the Apple problem, as I can only suspect that iBooks is now coded to identify that word in scripting files and then ignore those files.
They all make reference to the name 'edge'. Clearly there was some experimentation to be done (by one without much experience with this stuff!) but I stopped very early into it when I looked at the output files from Edge Animate.
Adding text in pubcoder zip file#
Then once saved, opening the EPUB zip file and adding the extra media files, plus updating the manifest information (list of files), after copying this from the list output from Edge Animate if you choose to export for iBooks. Like you, I thought there must be a way to overcome the problem by NOT inserting the OAM file but instead inserting HTML5 into InDesign ( then including the JS files when outputting the file to EPUB3. In fact, I'm a relative novice to the world of HTML etc. If you want to see the tone used in the Apple forum on this topic, check out the responses from 'K T' here: which Adobe thought it could overcome with HTML5 animations, but now Apple has found a way to nip that one too - by not supporting anything made in Edge Animate). I'm no expert but it appears that Apple have it in for Adobe (starting with the bold move to not support Flash.
Adding text in pubcoder update#
I'm waiting for an update on this item too.
0 kommentar(er)
