Tech Talk: Custom eBooks – Pride and Prejudice

il_570xN.451882126_jw4l

Bonjour all! So here is the status on this week: Today, we talk about customized eBooks (more specifically Pride and Prejudice) and Thursday I’ll give you tips on making delicious French Crepes! Which by the way are far less daunting … Continue reading 

Tech Talk: Adding audio files to EPUB3 books.

Well due to an issue with the Design Desk Blog at Chronicle my guest post on eBook design may not be up until next week. I’ll keep you all posted and put up the link when it’s ready!

In the meantime lets talk about audio files in ebooks. Last week I gave myself a crash course in SMIL files for a Children’s eBook I’m working on. It was a tall order, at 5:30pm on a Thursday I was asked if I could have read-along audio (already recorded) ready for a brand new, EPUB3 fixed format book… by 3:30pm Friday.  I jumped right on it, I love pushing the eBook envelope and if I can help integrate extra features into eBooks for regular use, well that’s just icing on the cake. 6 hours later I had done it (and embedded video but that’s a story involving HTML5) and you’ll see it soon on the market.

Here’s what I offer you today, a checklist of things needed to make a successful SMIL media overlay (something I wish I had while muddling through tutorials) and a little background info.

So I went home and learned all about SMIL files. SMIL or Synchronized Multimedia Integration Language files are nothing new and are being integrated more and more into eBooks. I decided on the SMIL file mainly because the IDPF and the W3C condone it’s use and it’s supported by major EPUB3 platforms like Apple’s iBooks. The biggest reason though, was that a SMIL file doesn’t alter the EPUB content itself, meaning if an eReader doesn’t recognize a SMIL file it should still read the eBook without issue (this is also a part of the standard).  I’m a big supporter of having one EPUB for all platforms so that versatility was really attractive.

SMIL Checklist:

  1. Have your audio ready in its own folder in your OPS 
  2. Declare your audio in the package.opf, MP3′s are quite reliable and should have media-type=”audio/mpeg”
  3. Once your audio is declared it’s time to start making your SMIL files **Make one for each XHTML**. For a full look at how a SMIL File is formatted see this Google Code page with lovely examples.
    1. Don’t forget to include clipBegin=”0:00:00″ clipEnd=”0:00:00″ times for each audio clip
    2. Tying your audio start points to a paragraph ID is important, it allows for a text highlight and when readers touch specific text it will re-read it for them.
    3. Save with a .smil extension
  4. Once you have your SMIL files completed, it’s time to declare them in the package.opf with media-type=”application/smil+xml”
  5. Next, you’ll need to associate the SMIL files with the xhtml files they connect to (so the ereader knows which clip to play) You do this in the OPF by adding  media-overlay=”opf ID of SMIL file here to the end of the html file declaration it relates to. It should look like this:
    • xhtml” media-type=”application/xhtml+xml” media-overlay=”r000″/>
  6. Almost done! This is the part often skimmed over in tutorials. in the package.opf’s metadata section you must declare the total media time for each SMIL file and the   total duration for all media files. It should look something like this:
    • <metadata>
      <meta property="media:duration" refines="#r000">0:00:06</meta>
      <meta property="media:duration" refines="#r001">0:00:06</meta>
       <meta property="media:duration">0:00:12</meta>
       <meta property="media:narrator">Narrator name</meta>
       <meta property="media:active-class">-epub-media-overlay-active</meta>
      </metadata>
    • The last two metadata lines define whom the narrator is and what the active class is named when the read-along feature is turned on (so you can alter the CSS and change the text highlight color).

Finally–test it!  You’ll see a little sound option in the iBooks toolbar. Press “Start Reading” and if everything’s done correctly you’ll hear your audio. SMIL files should also validate without issue so you can always use epub check on your files to double check.

And of course feel free to ask questions!

**UPDATE: This SMIL setup has been succesful in iBooks, Sony’s eReader app, and been accepted by Google Books,  and I believe Kobo pending QA**

Tech: Embedding HTML5 Video in eBooks and what will support it

You wouldn’t believe how easy this is. Well, I suppose those who have already done it would but for those of you who haven’t, fear not! You’ll be a pro in about 2 minutes.

HTML5 allows for stunningly simple embedded video and audio in websites and EPUB3 eBooks. Be forewarned though you forward thinking eBook Developers only certain systems can/will support your HTML5 masterpieces.

The current list of devices that support EPUB3 are (let me know if you’ve heard of more!):

  • iBooks
  • Web-based reading platforms
  •  many app based readers can – check the stats on your specific concern

Devices working to have fully functioning EPUB3 capabilities:

  • Kobo (caution here – Multiple SMIL setups per page are hard for the KOBO, it may drop sound clips sporadically)
  • Sony (only via app)

And by way of major eReaders that’s about it. Kindle is slowly adding features in their own .mobi language and Barnes and Noble’s Nook has its own software for making enhanced eBooks that they prefer developers use.

But I digress, this is all you need in the HTML to embed a video (after it’s in your EPUB folder of course – this piece of HTML pre-supposes that you’ve placed the video clip in a file named “video”). Note that “controls” piece inside the tag, that auto embeds controls in your video so that the reader can stop and start the clip and make it full screen.

<video id="videopurple" controls="controls">
 <source src="video/yourvideo.mp4" type="video/mp4"/>
 <div class="errmsg">
 <p>Oops! Your Reading System does not support (this) video.</p>
 </div>
 </video>

Now on to the content.opf, just declare your video the way you would for any image:

<item id="videopurple" href="video/yourvideo.mp4" media-type="video/mp4"/>

And of course there’s the CSS, you can define the look of the video tag just like any other or like me, you can apply a special ID to your individual videos, affording you the opportunity to alter them individually.

#videopurple {
 display:block;
 width: px;
 height: px; 
 margin:auto;
 margin-top:20%;
}

And there you have it! That’s all it takes! If your readers are in a specific market, be sure to test on the specific device (of course, look who I’m talking to- you guys know this stuff). Also, that nifty div class=”errmsg”, yeah that will tell readers if their device won’t support video. You can style it like anything else:

.errmsg { 
 color:red;
 font-weight:bold;
 /* margin-left: -5em; */
}

Other than recommending you use .MP4 for your videos (and possibly also embed a fallback .ogg video – to do this just add a second “source” line in your HTML) that’s all you should need. I do recommend you keep your video embeds fairly simple for the time being, the higher the level of complexity, the more likely you are to run into trouble. That’s not to say you’ll always be limited in terms of complexity but, while eReaders are catching up to the standard, we’re woefully stuck in a middle place.

Enjoy, and let me know if you think something should be added!

You can also check out my guide to using SMIL files in eBooks.

Learning to Cook, Online cooking schools

Appetites

So we’re a little off schedule here at Foodie By Night, change is afoot and once the dust settles I just may tell you why. So forgive the delay, an article will be up tomorrow as per usual! Today is … Continue reading 

Blogs and Copyright: tips to make sure you’re credited

The internet is more or less the Wild Wild West of Copyright (If anyone else pictures Will Smith in Cowboy duds when I say this then kudos) and I have seen bloggers repeatedly ask for the same advice how do I keep my content my own? How do I stop others from stealing it. The short answer is: You don’t. Don’t get me wrong you have every right to your own content and there are ways to take action against those who steal your words and claim them as their own (and we will go over them) but let me help reduce your stress. You place your content on the internet to be shared right? Otherwise we’d all have private blogs. A cost of publicly sharing your ideas and your words is a constant battle with copyright infringement and plagiarism. So I propose this outlook, don’t worry about your content appearing other places, fight for proper accreditation instead.

What do I mean? By asking others to properly accredit your content to you and post a link they are actually directing traffic to you, they are spreading your message. And it is far easier to ask someone nicely to fess up that it is your content than it is to stop them from putting it up. But as we all know there are those offenders that simply can’t be dealt with when they won’t respond.

A quick list of accreditation and copyright tips:

  • Check your site’s comment section or inbox: Many polite bloggers will actually ask if they can use your content and if you didn’t reply, they may have taken that as an okay to post your material.
  • Know your rights: Do a little research on the copyright status of whatever content is in question as the rights are slightly different for everything. Art and images are pretty absolute but recipes, for example, have less rights attached to them (you cannot claim copyright over a list of ingredients or “basic” instructions but any original written content like intros or in-depth instructions can be copyrighted).
  • Apply for an official copyright: One of the best ways to have a legal standing is to actually copyright your website with the US government. This will allow you to file a copyright infringement complaint with the US government and should prompt an investigation. You can also ask them copyright questions.
  • Ask nicely: When you first spot your photos or words on someone else’s site without your permission or in a way you do not approve of, reach out to them first. Use the comments section, the contact page, or when all else fails use a service like WhoIs to get an email address for whomever owns the website. Many times a copyright infringer is simply an admirer that wants to share your posts with their friends, save it for themselves to read later, or they consider themselves a “collector” of blog posts around the web. As infuriating as this can be, try to hang in there and ask in a friendly way that they either take it down or that they provide your name as the author and a link to your blog/website. 
  • Warn: If your still having trouble or there is a repeat offender in your midst send them a warning and let them know that if they do not honor your wishes that you will have to register a complaint the Internet Crime Complaint Center (www.IC3.gov) or if you’re not officially copyrighted, the infringer’s ISP host. Another option is to send an official DMCA takedown notice which does not require that your website be copyrighted.
  • Add your name to photos: Using Photoshop add your name or web domain name to the photo. Try to place it somewhere where it can’t easily be cropped out.
  • Work with social media: Let’s face it, if you take nice photos, they’ll circulate. Post your photos to Pinterest, etc. straight from your website. Then it will track back to your website and at the very least establish a precedent that it is your photo.
  • For Companies, find their Copyright complaint site: Many major internet companies now provide copyright infringement reporting tools for their sites. Someone else using your picture on Facebook? They’ve got a solution. Copyright issues with Google or any of its satellite sites like YouTube? Google’s got a reporting tool too. But if you’re filing a complaint against Google or Facebook themselves and not a user be sure to read the Terms of Agreement in full first.
  • There’s always a Lawyer: If someone’s ripping you off in a big way or has just puzzled you, it never hurts to talk to a lawyer (well, except maybe your wallet). See if a family member or friend in Law has some recommendations for you.

My major take away from my experience on the web is that it is for sharing ideas socially. I’m putting up my tech posts so that other people will use and build on them. I want  it to be in circulation because honestly, especially in the world of tech and recipes, very little is “new”. Someone else did something similar somewhere and I’d like to make life easier for those techies out there looking for a little help building their SMIL files and whatnot. Everything I post I do so with the knowledge that ownership on the internet is hard to control and I do my best to work with those who like what I write. And I provide a contact page so that I can be contacted in case of any issues arising with my own site. Which coincidentally has led to more people properly and politely asking to use my content.

Ultimately, it’s your ideas and your thought processes. That is not something that someone else can have access to. Meaning if they try and even succeed in taking your content, they won’t actually have the skill to back up that claim and sooner or later will be found out, especially if they are getting attention for your work. My advice is to do your best to get the credit you deserve and take it as a compliment (albeit an annoying one if they didn’t ask first) whoever it is obviously thinks you’re producing good work.

Tech Talk: Why should the eBook be constrained to act like a book?

Beer Makes Daddy Strong

Those who build eBooks are faced with an interesting puzzle. Why build eBooks to look just like their print counterparts when they can do so much more? Ebooks can include audio (see my earlier post on SMIL files) or video, … Continue reading