With enough research, testing, and tweaking, it’s possible to create an ePub file that works reliably across reading systems. Having multiple ePub files of the same book for different reading systems makes the process onerous, especially when ePub files are being created in addition to other formats like print and web and each additional file variation requires its own QC review process. To keep the process manageable, our goal is to come up with a single ePub file that works consistently across as many reading systems as possible.
Some readers handle ePub3 markup well, while others are not even able to link to HTML5 elements. CSS rendering differs across reading systems and there’s a varying level of support for the ePub3 spec. One of the biggest challenges to creating ePubs is reader fragmentation. Other issues, such as reader fragmentation, further complicated matters. We did not want to lose the semantic tagging from our source XML inside our ePub files, which limited our ability to use many shortcuts or hacks to get the visual display of our ePubs exactly as intended.
#Where is the caret symbol on kindle fire 7 code#
It turns out the actual process of writing the XSLT code is one of the easier tasks in this workflow. The remaining task sounds simple: create an XSL workflow to transform XML to XHTML5. Having already adopted NLM 3.0 for book content and MathML for equations, much of the infrastructure for an XSLT workflow was in place.
The content resides in the ePub file as XHTML5, which makes it possible to create all the content files with XSLT. It is an open standard, it is accepted by many distribution channels, and it can contain rich media. In the interest of making this new study material flexible and as widely available as possible, we could not be limited by a print-first workflow and a print layout–based e-book. Our organization has a number of book series published in an NLM 3.0 XML-first workflow, including a new study program designed to be interactive and mobile-friendly.
0 kommentar(er)
