Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
ePubs-RollYourOwn(for_supercon2012)
1. ePubs in (early) 2012
Walter Lewis & Diane Bédard
OLA SuperConference 2012
2. Standards?
What is ePub?
spec defined by IDPF - International Digital Publishing
Forum
Who is IDPF? adobe, google, overdrive, kobo, sony,
world blind union, random house, daisy etc
… a trades group, not a standards group
PREVIOUS - ePub 2.0.1 (2010)
CURRENT - ePub 3.0 (Oct 2011)
4. Scholarly?
foot notes VS end notes
citation?
anchors for a reference?
embedded milestones to cite from?
need for back links (not there yet)
5. ePub3 Philosophy packaged HTML content
audio,
video, objects, colour
fixed layout – working group
tablet-like devices (high end)
6. ePub3
incorporates features defined by CSS3 Modules and
introduces EPUB-specific CSS constructs.
defines a restricted subset of SVG 1.1
defines a set of extensions to the W3C HTML5
document model that Authors may include in XHTML
Content Documents.
requires XHTML Syntax of HTML5 (5 unfinished)
scripting and form support are optional
… a conformant Reading System might not be a fullyconformant HTML5 User Agent
7. ePub3
It is highly likely that this will render obsolete the
current crop of "one-trick pony" light ePub readers
(sony, kobo etc)
Enter the tablet… full colour, full motion, add apps,
multimedia.. Moved beyond “just the book”
8. iBooksAuthor (.ibooks file)
Apple extension (proprietary)
iPad running iBook app
fixed layout (no re-flow)
accessibility: audio vs. font size
targeting textbook market
distribution/marketing rights?
9. DRM (don’t really mean it?)
Four main ebook DRM schemes at present:
Adobe's Adept DRM (overdrive, sony)
Apple's Fairplay DRM (ibook)
Barnes & Noble's DRM (nook/kobo)
Amazon's DRM (kindle)
…and “removers” readily available ;-)
12. Apps we suggest Software (mac/win/linux):
Calibre:
ePub Convertor and packager, epub reader
Sigil:
a dedicated EPUB editor
Adobe Digital Editions:
ePub reader, DRM tester (no linux)
Dreamweaver or any clean markup editor
13. Structural thoughts #1
reader app has driver’s seat, will show all content and
likely ignore some design
XHTML and CSS **MUST** be UTF-8 or UTF-16 BOM
so make sure your editor of choice does this /ensure you
SAVE as this format
supply all elements (internal to pub package) , not
externally linked
14. Structural thoughts #2
image element (inline)
formats allowed are .gif, .png, .jpg, .svg
alt tag REQUIRED
object element for anything else
(very weak support for this element)
Optimal image sizes (OPTIMIZE for WEB)
15. Optimal image sizes
reminder to OPTIMIZE for WEB
cover images:
590 pixels wide x 750 pixels high
resolution should be 72 pixels per inch (ppi)
color images saved in RGB colour space
format can be JPEG, GIF, or PNG.
Max widths for inside images:
Small mobile screens - assume 320 px wide
dedicated readers - assume 590 px wide
31. Distribution
•Put in your library website
•Bonus points – point to it in the
catalogue (marc 856 tag)
•Upload to iBooks
•Sell to Amazon
•ePub hosting sites
•OPDS – RSS-like feed for ePub
34. What to watch…
•Evolving standards…. to ePub3/HTML5
•Fixed layout format push for specialized formats
•Rise of the tablet – to handle new medias
•Re-purposed browsers, rather than built-up
reader apps
•DRM issues
35. Learn more…
ePubs Made Easy:
OLA Educational Institute – 3 weekly sessions
( April 25 to May 9)
… online – with homework! ;-)
Hinweis der Redaktion
Today we are working within the limitations of ePub 2.0.1 (2010) The fixes for some of these limitations are currently out as proposal for EPUB Open Container Format (OCF) 3.0 :aligned with HTML5… plus inclusion plans for audio, video, MathML, text-to-speech (volume, speed, pitch, rate, lexicon pronunciation dictionary), fonts (Open Type and WOFF), syncing audio to text, citation via CFI (canonical fragment identifiers [ICK!!]), integration of CSS2.1 (and limited bits of CSS3)
Philosophy – write once/read anywherelots of devices/same filescreen agnostic… screen flow regardless of size>>> which means a design-rich layout is NOT guaranteed, not even likely… style as "hints", not as necessary - get over it
Philosophy – write once/read anywherelots of devices/same filescreen agnostic… screen flow regardless of size>>> which means a design-rich layout is NOT guaranteed, not even likely… style as "hints", not as necessary - get over it
(NOTE: still pending full adoption, and then needs full vendor/hardware/software take-up … so likely 18-24 mos away) SO > consider ePub as moving target (like a browser), not locked (like a gadget)
(NOTE: still pending full adoption, and then needs full vendor/hardware/software take-up … so likely 18-24 mos away) SO > consider ePub as moving target (like a browser), not locked (like a gadget)
Philosophy – write once/read anywherelots of devices/same filescreen agnostic… screen flow regardless of size>>> which means a design-rich layout is NOT guaranteed, not even likely… style as "hints", not as necessary - get over it
In an ePub package an optional file with the reserved name rights.xml may be included within the META-INF directory at the root level of the container file system.This file is reserved for digital rights management (DRM) information for trusted exchange of Publications among rights holders, intermediaries, and users. If the META-INF/rights.xml file is present, its contents should be only namespace-qualified elementsThe rights.xml file must not be encrypted.If you need a rights file for royalty, loan period, limited plays, etc deal directly with the vendor you will be with.(sample DRM Rights.xml and signatures.xml on Jump Drive)
Structure diagram code snippet sample of opf - EPUB Open Publication Format Structure of an ePub - folders and nested folders--ZIPPED Container- mimetype (must be uncompressed) META-INF container.xml *** rights.xml if have DRM OPS (Open Publication Standard) book.opf (open publication format) chapter1.xhtml ch1-pic.png css style.css myfont.otfepub navigation document now required (toc.ncx deprecated)***** In an ePub package an optional file with the reserved name rights.xml may be included within the META-INF directory at the root level of the container file system. This file is reserved for digital rights management (DRM) information for trusted exchange of Publications among rights holders, intermediaries, and users. If the META-INF/rights.xml file is present, its contents should be only namespace-qualified elements The rights.xml file must not be encrypted.If you need a rights file for royalty, loan period, limited plays, etc deal directly with the vendor you will be with.
clean valid html 2 / xhtml markupavoidance of self-closing tags where possible for mobi devices (Amazon/OverDrive) … >> calibre will *fix* a <br/> for you by auto-adding an opening <br> when you export to a mobi device… don't sweat it.Character support… get the unicode right… but don't expect all character sets and fonts will actually work No support for MathML… so equations/symbols as bitmap or svg images
BOM = byte order mark
size of picture… both for size of file, but also with different device screen sizes … how to deal with resizing?how text wraps around image? (inline only for sure, *maybe* "float" will work )Talk about the sample B&W line drawing graphic novel from Overdrive every page is full graphic, download is 21 MB for 100 pages even though everything as picture>>> the one way to have absolute control over layout..
DOC to HTML to Calibre (lots to clean up in HTML bloat- calibre dodges)DOC to ODT (Open Office) to Calibre (less to clean up)DOC to HTML to DREAMWEAVER (use the clean MS HTML command) >>>>>>>>>> Sigil/CalibreWIN Word 2010 ONLY - install Aspose.Words for Microsoft Word >> EPUB format will be listed in the Save As dialog
IPPF validator not functional in Jan 1012… but expect it will be the best in the long run… as from the folk who write the standard