XML and EPUB
•Download as PPTX, PDF•
0 likes•3,063 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.
![In association with SO, WHY ARE WEDOING THIS AGAIN? ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (16)
Viewers also liked
Viewers also liked (20)
Similar to XML and EPUB
Similar to XML and EPUB (20)
Recently uploaded
Recently uploaded (20)
XML and EPUB
- 1. XML and EPUB Prerequisites for the future NIC GIBSON, CORBAS CONSULTING nicg@corbas.net www.corbas.co.uk
- 5. Uses a tag based structure to describe content
- 6. Readable by both humans and computers
- 9. Queryable
- 13. Authors use Word
- 15. You can try a style-based approach
- 20. Why EPUB?
- 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)
- 37. By hand
- 42. Simple design helps too
- 44. It’s not the same as web design
- 45. Create an eBook design
- 47. XML can make proofreading easier though!
- 49. Fonts are a problem
- 51. Doing it again is easy
- 52. Some content is hard
Editor's Notes
- 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
- 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 & maxwell, OUP)