XML and EPUB
Download as PPTX, PDF0 likes3,116 views
This document discusses converting content to XML and EPUB formats. It addresses: - Motivations for moving to these formats, like cost reduction and multi-format publishing. - XML is a text-based markup language that tags content to make it readable by humans and computers. It allows custom or standard languages. - EPUB has become a common e-book format, supported by readers like Kindle, Nook, iPad and others. Content can be converted to EPUB from XML or other formats. - The process involves issues like permissions, fonts, automation, quality control and design considerations that are different from print or web. Providers can help with the conversion process.
XML and EPUB
- 1. XML and EPUBPrerequisites for the futureNIC GIBSON, CORBAS CONSULTINGnicg@corbas.net www.corbas.co.uk
- 2. In association withSO, WHY ARE WEDOING THIS AGAIN?Cost reduction
- 4. Incremental sales opportunitiesREVISION NOTE – WHAT IS XML?A text-based mark-up language
- 5. Uses a tag based structure to describe content
- 6. Readable by both humans and computers
- 7. Create your own language or use a standard oneXML – A NEUTRALFORMATThe ultimate transfer format
- 9. Queryable
- 10. AutomatableGETTING THATCONTENT INTO XMLConvert existing content
- 11. XML should simply be part of the workflowfor new contentAPPROACHES TOEXISTING CONTENTManual conversion
- 12. Automated conversionWHAT ABOUTNEW CONTENT?What format is it in?
- 13. Authors use Word
- 14. How can we get it into somethingmore useful?WORD TO XMLThere are tools for this
- 15. You can try a style-based approach
- 16. You can try an “AI”-based approachTHE OLD WORLD WORKFLOW
- 19. NOW WE’VE GOTSOME XML...We can create some EPUBS
- 20. Why EPUB?
- 21. Can be an intermediate formatWHY EPUB?iPad
- 22. Sony Reader
- 23. B&N nook
- 24. Springalex
- 25. iPod
- 27. iRiver Story
- 28. (Kindle)
- 29. Digital Editions
- 30. Stanza
- 31. Firefox
- 32. Ibis Reader
- 33. Bookword
- 34. (iBooks)
- 35. and more...HOW?Automated conversion from XML
- 37. By hand
- 38. Proprietary applicationsfrom suppliersHOW TO DO ITWELL?Automation
- 40. Quality controlAUTOMATIONXML to EPUB can be automated
- 42. Simple design helps too
- 43. See Stilo Whitepaper“Pitfalls onthe Path from Print to EPUB”DESIGNIt’s not the same as book design
- 44. It’s not the same as web design
- 45. Create an eBook design
- 46. Involve techies, but don’t let us drive it!QUALITY CONTROLIt’s not the same as proofreading
- 47. XML can make proofreading easier though!
- 48. Not only does it need to look right, the implementation is importantTHINGS TO REMEMBERPermissions for backlist materials
- 49. Fonts are a problem
- 51. Doing it again is easy
- 52. Some content is hard
- 53. There are companies thatcan helpFREE WHITEPAPER“Pitfalls on the Path fromPrint to EPUB”Looks at some of the issues publishers need to be aware of when attemptingto automate the conversion of contentto EPUBSee also stilo.com/migrateVisit Stand Z575to request your copy
Editor's Notes
- #3: 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 & 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
- #5: 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)
- #7: 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.
- #9: Ken ???? from Cengage – small number of styles
- #20: 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 & maxwell, OUP)