XML and EPUB<br />Prerequisites for the future<br />NIC GIBSON, CORBAS CONSULTING<br />nicg@corbas.net  www.corbas.co.uk<b...
In association with<br />SO, WHY ARE WEDOING THIS AGAIN?<br /><ul><li>Cost reduction
Multi-format publishing
Incremental sales opportunities</li></li></ul><li>REVISION NOTE – WHAT IS XML?<br /><ul><li>A text-based mark-up language
Uses a tag based structure to describe content
Readable by both humans and computers
Create your own language or use a standard one</li></li></ul><li>XML – A NEUTRALFORMAT<br /><ul><li>The ultimate transfer ...
Semantic content
Queryable
Automatable</li></li></ul><li>GETTING THATCONTENT INTO XML<br /><ul><li>Convert existing content
XML should simply be part of the workflowfor new content</li></li></ul><li>APPROACHES TOEXISTING CONTENT<br /><ul><li>Manu...
Automated conversion</li></li></ul><li>WHAT ABOUTNEW CONTENT?<br /><ul><li>What format is it in?
Authors use Word
How can we get it into somethingmore useful?</li></li></ul><li>WORD TO XML<br /><ul><li>There are tools for this
You can try a style-based approach
You can try an “AI”-based approach</li></li></ul><li>THE OLD WORLD WORKFLOW<br />
XML LAST WORKFLOW<br />
XML FIRST WORKFLOW<br />
NOW WE’VE GOTSOME XML...<br /><ul><li>We can create some EPUBS
Why EPUB?
Upcoming SlideShare
Loading in …5
×

XML and EPUB

4,757 views

Published on

Nic's presentation on XML and EPUB from the London Book Fair 2010

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,757
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
67
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Expect that most people here have been hearing about the promise of XML for the last few years.There are a fair few things we’ve been promised. It should be cheaper to produce books this way – automation, repeatability.Starting with XML we can generate the app files and/or output files from the same source with a high level of automationPenguin – backlist conversion project – 3000 books to XML &amp; ePub for Sony Reader UK launchBA – new imprint with a novel business model looking to have a digital workflow from day one for flexibility and cost controlIncremental sales – easier to respond to new opportunities when you have AGILE content. Because XML can be queried
  • XML can be entirely formatting neutral, it can be entirely formatting based. It’s partially a corporate decision and partly a project specific decision as to where on a continuum you need to be. I would almost always try to have a semantic structure down as far as inline content and I’d mark up anything *important* in the inline content. Of course, only you can know what’s important in your books. But... the more semantic the content the more opportunities you have to create new uses for that content (the extent to which this is true depends greatly on what sort of content we’re talking about)
  • You need to know where your content is, what form it’s in, is it worth converting (not always). Conversion is a one off cost but still a cost.penguin converted 3000 backlist titles. How many are selling? Before you convert it, decide what you want to convert to.
  • Ken ???? from Cengage – small number of styles
  • Mention penguin issues with backlist materialsDiscuss poetry and drama. Line orientated text. Spread based layouts (hard to create XML anyway)Specifications are a requirement – ask the people who’ve done this a while (sweet &amp; maxwell, OUP)
  • XML and EPUB

    1. 1. XML and EPUB<br />Prerequisites for the future<br />NIC GIBSON, CORBAS CONSULTING<br />nicg@corbas.net www.corbas.co.uk<br />
    2. 2. In association with<br />SO, WHY ARE WEDOING THIS AGAIN?<br /><ul><li>Cost reduction
    3. 3. Multi-format publishing
    4. 4. Incremental sales opportunities</li></li></ul><li>REVISION NOTE – WHAT IS XML?<br /><ul><li>A text-based mark-up language
    5. 5. Uses a tag based structure to describe content
    6. 6. Readable by both humans and computers
    7. 7. Create your own language or use a standard one</li></li></ul><li>XML – A NEUTRALFORMAT<br /><ul><li>The ultimate transfer format
    8. 8. Semantic content
    9. 9. Queryable
    10. 10. Automatable</li></li></ul><li>GETTING THATCONTENT INTO XML<br /><ul><li>Convert existing content
    11. 11. XML should simply be part of the workflowfor new content</li></li></ul><li>APPROACHES TOEXISTING CONTENT<br /><ul><li>Manual conversion
    12. 12. Automated conversion</li></li></ul><li>WHAT ABOUTNEW CONTENT?<br /><ul><li>What format is it in?
    13. 13. Authors use Word
    14. 14. How can we get it into somethingmore useful?</li></li></ul><li>WORD TO XML<br /><ul><li>There are tools for this
    15. 15. You can try a style-based approach
    16. 16. You can try an “AI”-based approach</li></li></ul><li>THE OLD WORLD WORKFLOW<br />
    17. 17. XML LAST WORKFLOW<br />
    18. 18. XML FIRST WORKFLOW<br />
    19. 19. NOW WE’VE GOTSOME XML...<br /><ul><li>We can create some EPUBS
    20. 20. Why EPUB?
    21. 21. Can be an intermediate format</li></li></ul><li>WHY EPUB?<br /><ul><li>iPad
    22. 22. Sony Reader
    23. 23. B&N nook
    24. 24. Springalex
    25. 25. iPod
    26. 26. IREX Digital Reader
    27. 27. iRiver Story
    28. 28. (Kindle)
    29. 29. Digital Editions
    30. 30. Stanza
    31. 31. Firefox
    32. 32. Ibis Reader
    33. 33. Bookword
    34. 34. (iBooks)
    35. 35. and more...</li></li></ul><li>HOW?<br /><ul><li>Automated conversion from XML
    36. 36. Export from InDesign
    37. 37. By hand
    38. 38. Proprietary applicationsfrom suppliers</li></li></ul><li>HOW TO DO ITWELL?<br /><ul><li>Automation
    39. 39. Design – http://www.epubzengarden.com/
    40. 40. Quality control</li></li></ul><li>AUTOMATION<br /><ul><li>XML to EPUB can be automated
    41. 41. Consistent design helps
    42. 42. Simple design helps too
    43. 43. See Stilo Whitepaper“Pitfalls onthe Path from Print to EPUB”</li></li></ul><li>DESIGN<br /><ul><li>It’s not the same as book design
    44. 44. It’s not the same as web design
    45. 45. Create an eBook design
    46. 46. Involve techies, but don’t let us drive it!</li></li></ul><li>QUALITY CONTROL<br /><ul><li>It’s not the same as proofreading
    47. 47. XML can make proofreading easier though!
    48. 48. Not only does it need to look right, the implementation is important</li></li></ul><li>THINGS TO REMEMBER<br /><ul><li>Permissions for backlist materials
    49. 49. Fonts are a problem
    50. 50. Create a specification
    51. 51. Doing it again is easy
    52. 52. Some content is hard
    53. 53. There are companies thatcan help</li></li></ul><li>FREE WHITEPAPER<br />“Pitfalls on the Path fromPrint to EPUB”<br />Looks at some of the issues publishers need to be aware of when attemptingto automate the conversion of contentto EPUB<br />See also stilo.com/migrate<br />Visit Stand Z575to request your copy<br />

    ×